[Bug 8533] Unhandled page fault on write access / gethostbyname("") -> Winsock problem

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=8533

------- Additional Comments From [e-mail]  2007-13-06 08:41 -------
I switched to windows and download an Winsock Tracer

The first "connect" from the program returns "WSAEWOULDBLOCK". The Tracer's help
says this about it:

" this indicates an error code of WSAEWOULDBLOCK, then your application can either:

1. Use select() to determine the completion of the connection request by
checking if the socket is writeable,  or

2. If your application is using the message-based WSAAsyncSelect() to indicate
interest in connection events, then your application will receive an FD_CONNECT
message when the connect operation is complete."

--------

I can figure out the way to post a full XMR in windows winsock trace if you want it.

I'll switch back to linux to test your workaround.