Re: Xcode/gdb and Objective-C runtime errors/warnings
Re: Xcode/gdb and Objective-C runtime errors/warnings
- Subject: Re: Xcode/gdb and Objective-C runtime errors/warnings
- From: Phil <email@hidden>
- Date: Sat, 18 Aug 2007 23:22:06 -0400
Perfect! It did exactly what I was looking for.
Thanks,
Phil
On Aug 18, 2007, at 10:27 PM, Clark Cox wrote:
If you set breakpoints at: "-[NSException raise]" and
"objc_exception_throw", the debugger should stop when any such
exception is raised.
On 8/18/07, Phil <email@hidden> wrote:
I've introduced a problem somewhere in my code but am having a bit of
trouble tracking it down so I was wondering: is it possible to have
Obj-C runtime errors/warnings drop me into the debugger at the
offending code? In my case, I'm attempting to call [NSNull
floatValue] which of course won't work and results in
an ...unrecognized selector sent to... message. Is there a flag that
would treat this as an error and drop me into the debugger when this
happens?
--
Clark S. Cox III
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden