[Bug 38610] New: winedbg fails to start in some cases when an application crashes
https://bugs.winehq.org/show_bug.cgi?id=38610 Bug ID: 38610 Summary: winedbg fails to start in some cases when an application crashes Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: madewokherd(a)gmail.com Regression SHA1: 2005be6dc92c0943ede01525cecad88f8e83c9c7 Distribution: --- I noticed this problem in a few cases: when certain application/game crashes the last line written in the terminal is something like this:
wine: Unhandled page fault on write access to 0x7e09e28c at address 0x7b853a3f (thread 002a), starting debugger... then winedbg simply quits without generating the backtrace/module list.
Reverting the following commit fixes the issue: 2005be6dc92c0943ede01525cecad88f8e83c9c7 is the first bad commit commit 2005be6dc92c0943ede01525cecad88f8e83c9c7 Author: Vincent Povirk <vincent(a)codeweavers.com> Date: Wed Apr 16 15:50:37 2014 -0500 shell32: Use CREATE_NEW_CONSOLE when SEE_MASK_NOCONSOLE is omitted. After reverting the commit winedbg is starting as expected: http://pastebin.com/4GRTtLaR (that's a game installer that crashes) Tested in wine-1.7.43-25-g0d91274 Fedora 21 x86 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #1 from Sebastian Lackner <sebastian(a)fds-team.de> --- Is there a publicly available app which triggers this problem reliably? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 --- Comment #2 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Sebastian Lackner from comment #1)
Is there a publicly available app which triggers this problem reliably?
I have yet to find such an app which is publicly available. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 --- Comment #3 from Vincent Povirk <madewokherd(a)gmail.com> --- Do you not get a crash dialog? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 --- Comment #4 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Vincent Povirk from comment #3)
Do you not get a crash dialog?
I completely forgot about the crash dialog because I always disable it in the first place after creating a wineprefix. So the problem occurs when the crash dialog is *disabled*. Backtrace is shown properly when the crash dialog is enabled. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 --- Comment #5 from Vincent Povirk <madewokherd(a)gmail.com> --- I'm guessing it's just not getting to your terminal because winedbg prints to the win32 standard output, which was (probably correctly) detached by ShellExecute starting with that commit. There's no reason to expect the stdout stream winedbg inherits from random crashing processes to always be useful, maybe it's a bug that the backtraces go there rather than the Unix stdout. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://files.na.mcneel.com/ | |rhino/4.0/2011-03-09/eval/r | |h40eval_en_20110309.exe --- Comment #6 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Rhino 4.0 installer from bug #17823 crashes at the end of installation. With disabled crash dialog terminal output ends with:
wine: Unhandled exception 0xe06d7363 in thread 41 at address 0x7b8397c4 (thread 0041), starting debugger... fixme:shell:SHChangeNotify ignoring unsupported flags: 2001
If I revert your patch then the backtrace is written too. Download: http://files.na.mcneel.com/rhino/4.0/2011-03-09/eval/rh40eval_en_20110309.ex... rh40eval_en_20110309.exe (134 MB) sha1: 921bd9f5df7b5fafb5920159109f4dc868932b27 wine-1.7.43-40-gf479071 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 --- Comment #7 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Still present in Wine 1.9.10. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 Vincent Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #8 from Vincent Povirk <madewokherd(a)gmail.com> --- I think it's reasonable to expect that if you change the default and turn off the crash dialog, you may not be able to find a backtrace. It was never a guarantee that you would, it's just coincidence that you used to get it and now you don't. If you don't want the crash dialog, and you do want the backtrace, you may have to put in more effort like manually attaching winedbg or starting the process through winedbg. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38610 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #9 from Austin English <austinenglish(a)gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org