http://bugs.winehq.org/show_bug.cgi?id=19300
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|winsock |-unknown
--- Comment #1 from Juan Lang juan_lang@yahoo.com 2009-08-07 16:54:42 --- Error 10035 is WSAEWOULDBLOCK, meaning there's no data to download. From the log:
trace:winsock:WS_socket af=2 type=2 protocol=0 trace:winsock:WSASocketA af=2 type=2 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=2 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 005c
Type 2 is SOCK_DGRAM, aka UDP.
Then: trace:winsock:WS_bind socket 005c, ptr 0x94ea38 { family 2, address 127.0.0.1, port 45301 }, length 16 (snip) trace:winsock:WSARecvFrom socket 005c, wsabuf 0x94db78, nbufs 1, flags 0, from 0x94dbf4, fromlen 16, ovl (nil), func (nil)
That is, it's expecting to get UDP packets from a local socket. I have no idea what it's expecting to receive there, nor from which program. I don't think this is likely to be a winsock bug, more likely some other program that's expected either to be present or to be run isn't there.