Re: Thread ID in debugger window versus console
Re: Thread ID in debugger window versus console
- Subject: Re: Thread ID in debugger window versus console
- From: Peter Duniho <email@hidden>
- Date: Tue, 3 Feb 2009 14:45:32 -0800
On Feb 3, 2009, at 12:37 PM, Jim Ingham wrote:
Well, I mean a Cocoa exception being thrown, so AFAIK not really
like "EXC_BAD_ACCESS" or a Unix signal. But yes, "something that
would cause your program to stop in the debugger".
By a Cocoa exception, you mean something thrown using [NSException
raise:] or objc_exception_throw? Like an array out of bounds error
or something like that.
I mean objc_exception_throw (in this case, NSInvalidArgumentException,
but I'm not sure it matters).
Raising an ObjC exception won't normally cause your program to stop
in the debugger unless you've either put a breakpoint on the throw
functions, or if the exception unwinds all the way and causes the
program to terminate.
The latter. The program does stop in the debugger, and gdb is in the
console pretty clear that it's because of the exception, not something
else interrupting the program at a later point.
Otherwise, you're probably stopping for some other reason later on
that's unrelated to the throw...
But if you can get me a log I can probably tell what went on...
I've submitted the bug report, complete with gdb log (and I've filed a
feature request bug on the gdb log preferences UI :p ). It is bug ID
#6552724.
Thanks!
Pete
_______________________________________________
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