http://bugs.winehq.org/show_bug.cgi?id=29168
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matteo.mystral@gmail.com
--- Comment #109 from Matteo Bruni matteo.mystral@gmail.com 2012-02-21 07:30:33 CST --- (In reply to comment #108)
(In reply to comment #106)
000d:trace:seh:raise_exception code=80000004 flags=0 addr=0x70a9c1 ip=0070a9c1 tid=000d
So I'm at an impasse again. I think I know what's going on; the IO thread crashes after getting the server header, never sending the reply, and another thread times out waiting for more data. But I don't see anything suspicious going on right before the crash, which means the trail is cold again.
This is not a crash, 80000004 is EXCEPTION_SINGLE_STEP, somebody is playing with CPU context flags?
Yeah, the thread initially doing the WSArecv actually generates those single step exceptions. Those happen on Windows too, AFAICT, and they don't seem to be a problem anyway (except making debugging more annoying, of course...)
Xolotl, you're right that the thread which calls WSArecv is not the same as the thread receiving the completion notification. But then this second thread posts an application-generated completion message to the first thread, which gets it. But nothing happens. The first thread also waits (non blocking) on a mutex which is never waited/signaled by other threads. That may play a role here, but it could also be completely unrelated.