Re: objc_exception_throw
Re: objc_exception_throw
- Subject: Re: objc_exception_throw
- From: Chris Espinosa <email@hidden>
- Date: Sun, 29 Jun 2008 15:11:28 -0700
On Jun 29, 2008, at 12:53 PM, Jens Alfke <email@hidden> wrote:
On 29 Jun '08, at 12:20 PM, Joan Lluch (casa) wrote: By setting a Breakpoint at objc_exception_throw or [NSException raise] I am able to stop my program when (for example) an out of range exception is thrown. However the call stack trace on the debugger window or the 'bt' command only shows a single line. For example:
I've also had this happen occasionally with various breakpoints (not just objc_exception_throw); I'm not sure what causes it or how to prevent it.
Is this in a debug or a release build of your app? Optimized code can sometimes lead to confused backtraces, although it should never get this bad.
A common cause of a truncated backtrace on exception handling is if your function somehow corrupted the return stack, which may also have caused the exception in the first place. A buffer overrun or bad cast on a function local is a common cause of this.
Chris |
_______________________________________________
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