Re: Xcode 4.3.1 doesn't show call stack
Re: Xcode 4.3.1 doesn't show call stack
- Subject: Re: Xcode 4.3.1 doesn't show call stack
- From: Joar Wingfors <email@hidden>
- Date: Thu, 22 Mar 2012 00:52:09 -0700
On 21 mar 2012, at 23:42, Quincey Morris wrote:
> On Mar 21, 2012, at 21:55 , Joar Wingfors wrote:
>
>> I love that feature, and use it almost all the time! I'd call it one of the more innovative and neat features of Xcode 4.
>>
>> I have to admit that I'm a bit surprised at your reaction to this feature. Why do you care to see frames from the innards of libraries that you don't have source code to? Admittedly, there are cases where that's informative / useful, but for the most part would you not rather focus in on your own code?
>
> Er, just for the record, I was just trying to make a feeble joke in response to Jens. Sorry if it sounded like a hate-o-gram.
>
> So, let me try to clarify by giving a serious response instead.
>
> I really do think the feature *sounds* like a good idea, but I've had the following experience:
>
> -- An app I'm working on throws an exception. Let's say it's a nib binding to an unknown property, something like that.
>
> -- With the level-of-detail slider in the central default position, the debugger display seems to be telling me that my app stopped in NSApplicationMain, since that's the only backtrace item listed for that thread.
>
> -- Because the debugger has stopped when the exception was thrown, nothing has been logged yet, so there's nothing on the console log to tell me why it stopped, or that it really *didn't* stop in NSApplicationMain.
Maybe there's something we can do to avoid this type of situation. Please file a bug report!
Thanks,
Joar
_______________________________________________
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