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: Mike Swingler <email@hidden>
- Date: Thu, 22 Mar 2012 08:57:23 -0700
On Mar 22, 2012, at 8:34 AM, Jens Alfke wrote: On Mar 21, 2012, at 11:42 PM, Quincey Morris wrote: -- 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.
Exactly. Here’s the problem with this feature: Many people (including me) have a first experience with it where they find out after some frustration that it’s lying to them by hiding the real cause of an exception/crash. Then they discover, by trial and error or by asking for help, how to turn it off. Then they say ‘good riddance!’ and leave it off.
It may well be that Joar is right and it’s useful to leave this on with the slider in an intermediate state where it shows some but not all of the intervening stack. (I do often find it very useful to know what system routine called into my code.) I’ll try that out.
But my suggestion is that the default state should be to turn this setting off, or at least leave it at an intermediate level that gives the new user some clue that information is being hidden from him/her.
It's possible that the heuristic could be adjusted to always show all frames from a point of interest (exception throw, breakpoint, etc) up to user-code, and then compress the rest of the irrelevant symbols. This could at least help with the "how the $*&# is my app crashing in main()!?!" frustration. Seem like a reasonable bug to log?
Regards, Mike Swingler Apple Inc.
|
_______________________________________________
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