http://bugs.winehq.org/show_bug.cgi?id=19706
Summary: app crashes when (exactly) WINEDEBUG=+snoop wine my-app.exe specified Product: Wine Version: 1.1.27 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: ericwertz@hotmail.com
I'm running an app under wine which otherwise runs without crashing (both under 1.1.27 and natively), except when I preface "wine my-app.exe" with "WINEDEBUG=+snoop" on the command line.
I found this originally by specifying "WINEDEBUG=+all wine my-app.exe" but narrowed the crash down to just "+snoop".
By crashing I mean that I get the nice "Program Error" dialog box that contains the text "This can be caused by a problem in the program or a deficiency in Wine..."
I am currently runing 1.1.27. I have not tried previous versions after 1.0.1. It does appear that the app crashes (unhandled exception) under 1.0.1, but runs fine natively.
The app in question is Full Tilt Poker (http://www.fulltiltpoker.com).
I'd normally include the log, but it's about 960Mb at the point where the crash occurs. Wine does not exit after closing the dialog box.
As this only affects tracing/debugging, it may not be the highest priority bug -- except that I've noticed in Bugzilla that one of the developer requests is to have +snoop turned on sometimes, which could complicate debugging.
http://bugs.winehq.org/show_bug.cgi?id=19706
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-11 23:09:27 --- It's normal with +snoop. Snooping is implemented by pure heuristics, if it hurts - don't do that. Neither +all nor +snoop are useful for wine debugging.
http://bugs.winehq.org/show_bug.cgi?id=19706
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-11 23:09:53 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=19706
--- Comment #3 from Eric B. Wertz ericwertz@hotmail.com 2009-08-20 23:13:19 --- (In reply to comment #1)
It's normal with +snoop. Snooping is implemented by pure heuristics, if it hurts - don't do that. Neither +all nor +snoop are useful for wine debugging.
I <i>guarantee</i> that "+all" is often critical for my particular use of wine, but now that I know that +snoop crash, I will certainly avoid it.
The fact that +snoop hasn't crashed on me before (nor in the last three years' worth of using Wine that I can ever remember), this suggests to me that it's a newly created crash and something that would be of concern to anyone that continues to actually want to trace snoop.
I personally would not consider +snoop crashes to be "normal".
http://bugs.winehq.org/show_bug.cgi?id=19706
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-21 04:19:33 --- (In reply to comment #3)
I personally would not consider +snoop crashes to be "normal".
Feel free to debug it.