On 2 Dec 2002, Martin Wilck wrote: [...]
I am currently having trouble with running stuff natively on Windows. Can anybody run the winsock test with verbose output (trace enabled) on Windows NT and send me the result ?
Here goes:
sock.c:686: **** STARTING TEST 0 **** sock.c:327:simple_server (b2) starting sock.c:386:simple_client (dd): starting sock.c:336:simple_server (b2) ready sock.c:389:simple_client (dd): server ready sock.c:341:simple_server (b2): waiting for client sock.c:386:simple_client (28): starting sock.c:389:simple_client (28): server ready sock.c:401:simple_client (dd) connected sock.c:341:simple_server (b2): waiting for client sock.c:422:simple_client (dd) exiting sock.c:401:simple_client (28) connected sock.c:369:simple_server (b2) exiting sock.c:422:simple_client (28) exiting sock.c:607: Test failed: some threads have not completed
sock.c:688: **** TEST 0 COMPLETE **** sock.c:686: **** STARTING TEST 1 **** sock.c:327:simple_server (a5) starting sock.c:336:simple_server (a5) ready sock.c:341:simple_server (a5): waiting for client sock.c:440:event_client (ce): starting sock.c:440:event_client (cc): starting sock.c:442:event_client (ce): server ready sock.c:451: Test failed: event_client (ce): connect error: 10022 sock.c:442:event_client (cc): server ready sock.c:451: Test failed: event_client (cc): connect error: 10022 sock.c:607: Test failed: some threads have not completed
sock.c:613:terminating thread 000000a5 sock.c:613:terminating thread 000000ce sock.c:613:terminating thread 000000cc sock.c:688: **** TEST 1 COMPLETE ****
There is no further output. The process does not terminate and has 1 remaining thread at this point.