http://bugs.winehq.org/show_bug.cgi?id=29168
Xolotl Loki xoloki@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #37997|0 |1 is obsolete| | Attachment #38016|0 |1 is obsolete| |
--- Comment #48 from Xolotl Loki xoloki@gmail.com 2011-12-18 19:16:12 CST --- Created attachment 38023 --> http://bugs.winehq.org/attachment.cgi?id=38023 WINEDEBUG=+winsock log with extra tracing on WS2_async_recv
Here I added some tracing in the async recv function. It looks like we are getting the 22 byte packet, and returning that result properly asynchronously.
But the next recv call also goes async, and the callback gets a result of 0. Next we close the socket.
Next I'll trace the entry points to WS2_recv_base, and see from where we're coming.