http://bugs.winehq.org/show_bug.cgi?id=29145
--- Comment #3 from Igor Urazov z0rc3r@gmail.com 2011-11-22 23:29:57 CST --- Erm, the things are actually contrariwise.
Bad: trace:winsock:WS_getaddrinfo (null), "51415" 0x32fa28 -> 0x32fa20 -2 trace:winsock:WS_getaddrinfo (null), "18050" 0x32fab0 -> 0x32fad4 -2 trace:winsock:DllMain 0x7e670000 0x2 (nil)
Good: trace:winsock:WS_getaddrinfo (null), "51415" 0x32fa28 -> 0x32fa20 0 trace:winsock:WS_socket af=2 type=1 protocol=6 trace:winsock:WSASocketA af=2 type=1 protocol=6 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=1 protocol=6 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 00c8 trace:winsock:WS_setsockopt socket: 00c8, level 0xffff, name 0x4, ptr 0x32fa18, len 4 trace:winsock:WS_setsockopt socket: 00c8, level 0xffff, name 0x1002, ptr 0x32fa18, len 4 trace:winsock:WS_setsockopt socket: 00c8, level 0xffff, name 0x1001, ptr 0x32fa18, len 4 trace:winsock:WS_bind socket 00c8, ptr 0x144ee0 { family AF_INET, address 0.0.0.0, port 51415 }, length 16 trace:winsock:WS_listen socket 00c8, backlog 5 ... trace:winsock:WS_getaddrinfo (null), "18050" 0x32fab0 -> 0x32fad4 0 trace:winsock:WS_socket af=2 type=1 protocol=6 trace:winsock:WSASocketA af=2 type=1 protocol=6 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=1 protocol=6 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 00dc trace:winsock:WS_setsockopt socket: 00dc, level 0xffff, name 0x4, ptr 0x32fadc, len 4 trace:winsock:WS_setsockopt socket: 00dc, level 0xffff, name 0x1002, ptr 0x32fadc, len 4 trace:winsock:WS_setsockopt socket: 00dc, level 0xffff, name 0x1001, ptr 0x32fadc, len 4 trace:winsock:WS_bind socket 00dc, ptr 0x142468 { family AF_INET, address 0.0.0.0, port 18050 }, length 16 trace:winsock:WS_listen socket 00dc, backlog 5 ... trace:winsock:DllMain 0x7e670000 0x2 (nil)