[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: objc_exception_throw

Subject: Re: objc_exception_throw
From: Jens Alfke <email@hidden>
Date: Sun, 29 Jun 2008 12:53:59 -0700
Delivered-to: email@hidden
Delivered-to: email@hidden

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.

—Jens

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden

Follow-Ups:
- Re: objc_exception_throw
  - From: Chris Espinosa <email@hidden>

References:
	>objc_exception_throw (From: "Joan Lluch (casa)" <email@hidden>)

Prev by Date: Re: Generating Random Numbers
Next by Date: Re: Project templates
Previous by thread: objc_exception_throw
Next by thread: Re: objc_exception_throw
Index(es):
- Date
- Thread

Home