Re: Breaking into debugger after program hangs....
Re: Breaking into debugger after program hangs....
- Subject: Re: Breaking into debugger after program hangs....
- From: Ondra Cada <email@hidden>
- Date: Thu, 28 Apr 2005 12:40:31 +0200
John,
On 28.4.2005, at 10:48, John Draper wrote:
Is there a way to break into the debugger when the program hangs? Is
it a
special key combination?
There's the "pause" ("||") nice small button in the GUI :) Also, ctrl-c
in the gdb console used to work pretty well, but that I haven't tried
for a long time.
And once in the debugger, how do I get the current stack trace using
gdb or source level debugger. To find out where it crashed....
Gdb is the source level debugger.
Anyway, in GUI there is a pane with the stack trace; in the console
enter "bt".
Is there a way to cause the application to break at a breakpoint
when I try and send a message to a de-allocated object?
I set NSZombieEnabled = YES, and I got...
Program received signal: "EXC_BAD_ACCESS".
Does not feel right, the problem would be elsewhere. If zombies
enabled, the program does not crash this way. It would report what
happened.
Then, the tech note says... You can use GDB to set a breakpoint on
-[_NSZombie methodSignatureForSelector:] to further debug this sort of
problem.
Before, of course. What's the point of setting a breakpoint *after* the
code crashed?
Nevertheless, I fear it won't break anyway, for, as said above, the
problem seems to be caused by something other.
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden