What is the best way to debug a freeze in wine?

[Stefan Dösinger]

Hi,

Trying to get a backtrace in the frozen state would have been my first
suggestion :-) The honest answer is that there is no way that guarantees
suceess. I can suggest a few things, but beyond that finding bugs is
always a case of trial and error, intuition and patience.

Fron the backtrace it seems that the game is waiting for some object
(WaitForSingleObject). Is the wait timing out, or is the object
available at some point? What object is this handle 0xaa8? My way of
finding out is to run a +relay log and look for the create or open call
that returned it (keeping in mind that it could be closed, and returned
by a different open call later), although there is probably a better way.

Since the bug is apparently specific to keyboard input you could look
for hints in related debug channels. I don't know which ones they are
though, but I'd try +keyboard,+dinput,+msg. If you have a mac you could
test it on macos to see if this is a winex11.drv specific issue.

Good luck,
Stefan

Am 2017-05-22 um 04:30 schrieb Derek Lesho:
> This is my first time posting in a mailing list, so if this is the wrong
> place to ask or I am doing something wrong, please tell me.  Anyway, In
> wine 2.8, GTA-V is able to be run, however there is a major bug in which
> any key press will freeze the game for a few seconds.  However, if you
> bind any actions to the mouse, say mouse4 or mouse5, the issue is not
> present.  GTA-V has also worked for people using xbox 360 controllers. 
> I have moderate programming knowledge, and I would like to find the
> source of this bug, however I have no found a good way to do it yet.  I
> have tried winedbg, however when I get a backtrace of the process, there
> are atleast 50 threads running and I am unsure which one is locking up
> the game.  I would use perf, however so far I haven't figured out how to
> make it tell me which functions are taking up most of the time.
> 
> My question is, do any of you know of good tools/techniques that would
> help me debug this sort of problem?  It would be greatly appreciated.
> 
> P.S. for any of you who are also interested in this specific problem,
> many error messages are sent out at a very fast speed, but when the game
> is frozen due to this bug, all error messages temporarily halt with the
> exception of these two:
> 
> fixme:keyboard:X11DRV_ActivateKeyboardLayout 0x4090409, 40000000:
> semi-stub!
> fixme:keyboard:X11DRV_ActivateKeyboardLayout flags 40000000 not supported
> 
> Which are output a slow interval instead until the game unfreezes at
> which point the console output returns back to its normal sporadic
> behavior.
> 
> Also, here is a normal backtrace from winedbg while the issue is
> occuring: http://paste.ubuntu.com/24539530/
> 
> 
>