On 3 Dec 2002, Martin Wilck wrote:
With the following fixes, the winsock test runs fine (0 errors) on Win NT (and Wine!).
I applied the patch but the test still fails and gets stuck on NT4:
sock.c:694: **** STARTING TEST 0 **** sock.c:332:simple_server (d3) starting sock.c:341:simple_server (d3) ready sock.c:346:simple_server (d3): waiting for client sock.c:391:simple_client (dd): starting sock.c:394:simple_client (dd): server ready sock.c:391:simple_client (b9): starting sock.c:394:simple_client (b9): server ready sock.c:406:simple_client (dd) connected sock.c:346:simple_server (d3): waiting for client sock.c:427:simple_client (dd) exiting sock.c:406:simple_client (b9) connected sock.c:374:simple_server (d3) exiting sock.c:427:simple_client (b9) exiting sock.c:696: **** TEST 0 COMPLETE **** sock.c:694: **** STARTING TEST 1 **** sock.c:332:simple_server (ec) starting sock.c:341:simple_server (ec) ready sock.c:346:simple_server (ec): waiting for client sock.c:445:event_client (ea): starting sock.c:445:event_client (e3): starting sock.c:447:event_client (ea): server ready sock.c:456: Test failed: event_client (ea): connect error: 10022 sock.c:447:event_client (e3): server ready sock.c:456: Test failed: event_client (e3): connect error: 10022
It stays there for a long time and then prints:
sock.c:456: Test failed: event_client (e3): connect error: 10022 sock.c:614: Test failed: some threads have not completed: 102
sock.c:621:terminating thread 000000ec sock.c:621:terminating thread 000000ea sock.c:621:terminating thread 000000e3 sock.c:696: **** TEST 1 COMPLETE ****
But then the process does not terminate...