http://bugs.winehq.org/show_bug.cgi?id=29168
Jason r6express@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |r6express@yahoo.com
--- Comment #81 from Jason r6express@yahoo.com 2012-01-05 13:44:41 CST --- 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.
Regardless, I forced a 10 second delay prior to the first read on the login port 8995 and this allowed it to read the first 22 bytes without going into the async operation. WS2_recv_base then correctly returns 0 and err is set to 0 as well. But the login data (1k chunk) still is not sent by the swtor process.
It's possible that there is some subtle difference between the wine and windows WSA implementations, but it's still just as possible that the swtor process is getting the full 22 bytes back into it's hands correctly and a follow-up error (without log) is occuring, such as a routine to compress or encrypt the 1k block that it is supposed to send back over the socket.