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: Jim Ingham <email@hidden>
- Date: Tue, 3 Feb 2009 12:37:23 -0800
On Feb 3, 2009, at 12:15 PM, Peter Duniho wrote:
On Feb 3, 2009, at 11:35 AM, Jim Ingham wrote:
I assume by exception you mean something like a EXC_BAD_ACCESS, or
some kind of UNIX signal? Something that would cause your program
to stop in the debugger...
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.
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. 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...
If so, then the debugger is always supposed to stop and show you
the thread where the exception occurred. If it's not doing that
that is a bug, and please do file a bug report on it.
Should it always do this for Cocoa exceptions? I mean, it's my
opinion it _should_, but I don't know whether the fact that it
doesn't now is by design or a bug.
It would be exceptionally great if you could include a reproducible
case in your bug. If you can't then at least turn on the Xcode-gdb
log (in the Debugging Pane of the Xcode Preferences) and include
the log in the bug you file. If you could also indicate which
thread you thought got the exception that would be helpful.
The exception occurs in the context of another hard-to-reproduce bug
in Cocoa. But I will do my best to get it to happen again, and then
provide a log for the case when it happens. The console output is
clear about in what thread the exception occurs, so that information
will be easy for me to include.
The console output all goes into the log as well. So you don't have
to provide that, just the gloss on it. Thanks.
Nice pun, by the way. I always appreciate a good pun. :)
Thanks...
Jim
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
_______________________________________________
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