libutp doesn't work on Windows 64-bit whith default timer about libutp

[ghazel]

Does the tests binary run without error? Do you see the same error when using the Visual Studio compiler?

It's true that we were only testing libutp with 32bit when it was written, but this sort of error seems odd.

One simple possibility is that mingw might not define WIN32 (I think we should instead be using _WIN32) in utp_utils.cpp. That would cause it to fall back to a mingw implementation of clock_gettime(CLOCK_MONOTONIC, ...), which might suck. Try defining WIN32 by hand and see if the MinGW-w64 build works.

[rb07]

Does the tests binary run without error?

No, they don't do anything, one side exits with an error message that means time-out on a socket; the other keeps going, doing I don't know what (the log file is just 3 lines, seems to be some statistics about some "states", first column has 0, 49, 31550, second 0x805BF0 in all 3 lines, third column has state 1, 2, 4 -- the other process didn't leave anything on the log).

Do you see the same error when using the Visual Studio compiler?

I don't use VS, and I don't intend to test it.

mingw[-w64] might not define WIN32

It does. But I will try your test, or put an #error if the fall back is used.

[rb07]

Using the debugger I see GetMicroseconds() is from utp_utils.cpp:55 (in Transmission version of the code), that means the correct function is called in Windows.

I'll try to see if not being monotonic is causing the problem.

[rb07]

Let's mark this report as invalid.

After more testing I could not detect any counter regression with the clock at either of the settings. And the application worked fine with both settings... so, the only thing I know is that I can't reproduce the problem, and that I don't know what caused the observed problem case.

One very unlikely cause of the observed problem (the dropping of all peers that used uTP) could be that I happened to connect to a few dozen peers running the same buggy version of uTorrent, the 3.0.0 version which I still see being dropped). Very unlikely.

Another possible cause may be the development environment. It is very quirky, I've seen crashes in other libraries that go away when I try to track them down... the problem is that I don't know if they are coming back, or when and where ... but that has nothing to do with libutp.

Thanks for your help Greg. Sorry for what appears to be noise.