[Bug 24524] Cannot disable the debugger

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=24524

Jörg Höhle <hoehle at users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hoehle at users.sourceforge.ne
                   |                            |t

--- Comment #5 from Jörg Höhle <hoehle at users.sourceforge.net> 2010-10-25 09:22:54 CDT ---
Somehow it's no surprise to me that the wish for disabling the debugger comes
up on MacOS.  I have observed cases where Wine behaved like a fork bomb: after
a crash, launching winedbg crashed, causing another instance of winedbg to be
started, crashing again ...
I believe Wine should include some protection against recursively starting the
debugger.  I don't know why, but I've seen this every now and then on MacOS but
at most once on Linux, so it's not only a MacOS issue.

IIRC, fork bombs occur when one of the two %ld values passed to --auto contain
garbage (cause of garbage unknown) or point to unusable/protected memory.

IMHO, if winedbg would manage to produce backtraces and then exit on MacOS as
reliably as it mostly does on Linux, the wish for disabling the debugger might
not emerge.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.