Bug #8950 2006-09-30 08:50
bnilsson
Mac OSX: "Stop debugger" causes violent crash
Platform:
Dual 2.3GHz G5
Mac OSX 10.4.8
wxWidgets 2.6.3
codeblocks rev 3001 installed by darwinports according to wiki instructions.
Open a wx project, start debugger, see the app run, quit the app.
Then select "Stop debugger".
Codeblock crashes, killing Finder and all other running applications.
- Category
- Application::Crash
- Group
- Status
- Closed
- Close date
- 2006-11-19 23:36
- Assigned to
- afb
History
For those of you that don not know, "Finder" is the Mac's window manager.
This is problem related to the other "Abort" bugs that we've seen, in that it kills the loginwindow.app instead of the child...
BTW: The Finder is Mac OS X infamous file manager, not the window manager. But it's still bad for it to die, of course :-)
This problems seems to be gone now that wxExecute is fixed/patched ?
Seems to be alive on kicking on PPC, so "reopening" the bug.
(though I did have some trouble reproducing it on Intel...)
It seems that wxMac is reporting a PID of "-1",
and when you kill that PID it means to killall...
The easy part is adding a check for PID == -1
in Debugger::GDB. Hard part is finding GDB...
(i.e. finding the process we want to terminate,
if wxExecute was lying about the process ID ?)
Should show an error dialog now, instead of killing everything...
(still need to actually stop the debugger, that'll be added later)