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 12:15:38 -0800
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".
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.
Nice pun, by the way. I always appreciate a good pun. :)
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