http://bugs.winehq.org/show_bug.cgi?id=29168
--- Comment #82 from Jeremy White jwhite@codeweavers.com 2012-01-05 14:56:28 CST --- (In reply to comment #81)
I don't see a valid completion function (arg is nil) or an event handler (arg is 0000) specified to the WSA recieve func, so I'm not sure how the caller is supposed to know that the async read has finished.
If you look a bit before the connect() call, you'll see a CreateIoCompletionPort call that associates the socket with an Io completion port. That is sufficient, on Windows, to provide a way to find those 22 bytes after they come in. I do see an indication that a GetQueuedCompletionStatus is called, and returns those 22 bytes, so we do seem to be correctly reporting that the 22 bytes arrive.