Breaking into debugger after program hangs....
Breaking into debugger after program hangs....
- Subject: Breaking into debugger after program hangs....
- From: John Draper <email@hidden>
- Date: Thu, 28 Apr 2005 01:48:06 -0700
Hi
Is there a way to break into the debugger when the program hangs? Is it a
special key combination?
My application crashes and hangs up, and I'm still very confused about
the details in TN2124... I have a few separate questions just on the
tech note.
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....
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".
[Switching to process 2912 thread 0xbe07]
[Switching to process 2912 thread 0xbe07]
Then, the tech note says... You can use GDB to set a breakpoint on
-[_NSZombie methodSignatureForSelector:] to further debug this sort of
problem.
Ok, so when do I do this, after I get the "EXC_BAD_ACCESS", then
do I do it, or do I set this breakpoint right when I start the program.
The Tech notes just mentions it. But it don't get into very much details
on where or when I can "further debug this sort of problem".
Is there any other debugging tips other then TN2124?
Right now, I just want to find out who or what deallocated an object,
and which one it was. Is this possible to do? Is there any source
of any step by step processes I can learn about? If so, where?
Any good recommendations on books? Ones which are easily available
in the LA area?
John
_______________________________________________
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