Re: Debugging & symbolic breakpoints
Re: Debugging & symbolic breakpoints
- Subject: Re: Debugging & symbolic breakpoints
- From: "Alastair J.Houghton" <email@hidden>
- Date: Sat, 16 Aug 2003 11:29:27 +0100
On Friday, August 15, 2003, at 09:56 pm, Jvrn Salewski wrote:
I know one can set a symbolic breakpoint at [NSException raise], but
is it
also possible to tell the debugger (hopefully from PB) to stop when a
'selector is not recognized'? It's logged to console, but is
apparently not
an Exception.
I think this message is caused by calls to the
-doesNotRecognizeSelector method on whichever object you are calling.
You can probably intercept it in most cases by placing a breakpoint on
[NSObject doesNotRecognizeSelector], although some objects may
implement custom handling in which case you might need separate
breakpoints for them.
Furrther on: Can one get a stack backtrace at the point where the
debugger
stopped - well, at least somehow to find out from where exactly the
code,
that triggered the debuger to stop, was called..?
Type "bt". It lists all of the stack frames visible to the debugger.
You can select a particular one to examine by typing "frame". Also,
the first time you type "list" after the debugger stops (or after
changing frame), you will see where in the code the processor stopped
executing the program.
There are *lots* of very useful commands in GDB; if you haven't already
done so, you should definitely have a read of the manual... you can
even do things like defining your own commands, declaring temporary
variables to use just whilst debugging code, set values to display
whenever the debugger stops (or at a particular breakpoint), etcetera.
Kind regards,
Alastair.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.