Re: C++ exception breaks inside Apple code
Re: C++ exception breaks inside Apple code
- Subject: Re: C++ exception breaks inside Apple code
- From: Jim Ingham <email@hidden>
- Date: Mon, 28 Sep 2009 16:16:08 -0700
The "C++ Exception Name" entry field in the C++ exception breakpoint
dialog Xcode is actually implemented as a regular expression match
against the class name of the exception (rather than just an exact
string compare.) So you might be able to put in something clever
there that stops on the exceptions you care about but not the ones
you're getting internally. This is the same as doing "set exception-
throw-type-regexp" in command line gdb, btw.
There isn't a "don't stop on exceptions thrown from library
"whatever.dylib" though that might be a useful addition.
Jim
On Sep 28, 2009, at 3:38 PM, Greg Guerin wrote:
James Walker wrote:
When I set a breakpoint on throw of all C++ exceptions, I often hit
a breakpoint inside OS code. I don't recall that happening before
Snow Leopard and Xcode 3.2. Was I just lucky before, or is
something broken?
All that's necessary is for the internal implementation to change in
a way that C++ exceptions are caught and handled internally.
Before, you were relying on an implementation detail: that
exceptions weren't used internally except to indicate unrecoverable
error conditions. You might call that lucky.
-- GG
_______________________________________________
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
_______________________________________________
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