socket question

michael cardenas michael.cardenas at lindows.com
Mon Mar 25 16:42:24 CST 2002


I'd like to throw this out there for anyone more familiar with sockets in 
wine than I am. Here's some of the output of running aol with --debugmsg 
+winsock:

trace:winsock:WS_socket af=2 type=1 protocol=0
trace:winsock:WS_socket 	created 0320
trace:winsock:WS_bind socket 0320, ptr 0x40595b7c, length 16
trace:winsock:WSAAsyncSelect 0320, hWnd 006f, uMsg 00000468, event 00000033
trace:winsock:WSAEventSelect 00000320, hEvent 00000328, event 01000033
trace:winsock:WS_connect socket 0320, ptr 0x40595b50, length 16
trace:winsock:WINSOCK_DoAsyncEvent socket 00000320, event 00000328
trace:winsock:WINSOCK_DoAsyncEvent post: event bit 4, error 10061
trace:winsock:WINSOCK_DoAsyncEvent socket 00000320, event 00000328
trace:winsock:WINSOCK_DoAsyncEvent post: event bit 5, error 0
trace:winsock:WSAAsyncSelect 0320, hWnd 006f, uMsg 00000468, event 00000000
trace:winsock:WSAEventSelect 00000320, hEvent 00000000, event 00000000
trace:winsock:WINSOCK_DoAsyncEvent socket 00000320, event 00000328
trace:winsock:WINSOCK_DoAsyncEvent orphaned event, self-destructing

this seems to happen over and over again. My application sets up it's socket 
to send it a window message when the event happens, but the event takes too 
long and so the app turns off the notification, and the event becomes 
orphaned. 





More information about the wine-devel mailing list