http://bugs.winehq.org/show_bug.cgi?id=31442
--- Comment #28 from voidcastr voidcastr@gmail.com 2012-10-03 05:15:34 CDT --- (In reply to comment #27)
Usually you should see what threads are involved in a deadlock. (I.e. "... wait timed out in thread <tid1> blocked by <tid2>, ..." messages.)
Yeah, I also found that here in the meantime: http://wine-wiki.org/index.php/Debugging_Wine
However, I made an observation: According to Wine-dbg's "info process"/"info thread", the number of threads spawned by the application varies depending on the usage of its -dx9single cmdline argument:
With -dx9single: 36 threads Without: 37 threads
(The above thread counts were obtained in the application's non-frozen state in both cases.)
This is not overly surprising and I'm currently trying to associate the threads of both cases with each other, in order to identify the extra thread in the second case and then analyze its trace. Sadly, I don't expect this method to succeed because tids are only partially deterministic and the BTs obtained while the application is not crashed/frozen also tend to vary greatly.
Interestingly, tids are the same after most application startups when NOT using -dx9single, while greatly varying when using the flag -- I actually expected the contrary (more parallel threads usually lead to less deterministic results).
or what you're seeing isn't so much a deadlock as the rendering thread just dieing.
Yep, but I still don't understand why -- if the rendering thread just dies -- it appears to be impossible to get some exception, segfault, ... anything at all.