http://bugs.winehq.org/show_bug.cgi?id=31442
--- Comment #20 from voidcastr voidcastr@gmail.com 2012-10-02 03:18:06 CDT --- (In reply to comment #18)
I can't really rule out occlusion queries, but I think it's more likely that this is some variant of bug 31406. A backtrace would probably help.
Mea culpa... I did not realize that you might have referred to a winedbg backtrace.
I tried to get one but the howto in the wine wiki (wiki.winehq.org/Backtraces) appears to be slightly outdated.
Here's what I've done:
1. start the application with "wine Gw2.exe"
2. open another terminal for "winedbg" -> "info process" -> "attach 0x...". So far so good.
3. then, using "set $!BreakOnFirstChance=0" in winedbg as suggested in the wiki does not work since it complains about a "Syntax Error ($) Unknown option 'BreakOnFirstChance' syntax error"
4. I entered "cont" anyway... but winedbg seems to block there, not showing me another prompt (until I hit Ctrl-C or run "killall Gw2.exe" from another terminal; see below)
From here, I'm not sure if I'm still on the right track and if the backtraces I
obtained this way might be useful at all:
5. I provoked the application freeze
6. winedbg was still blocking, so I hit Ctrl-C and got a backtrace with "bt"
7. if I "killall Gw2.exe" afterwards and winedbg>"bt" again, the backtrace changes
Now, I'm not sure if one of the backtraces represents the actual freeze bug/crash, or if one or both of them are just the reaction to the signal I sent with Ctrl-C or to killing the application, respectively.
Any corrections/comments on my approach? For now, I refrained from posting the above traces here because I don't wanna cause confusion in case they are useless.
(PS: My apologies if these are dumb questions... I'm still new to wine debugging stuff in general.)