title: What is the point of a Stack Trace in Xcode?
body: <p>Sometimes Xcode encounters an error - but rather than throw a proper "end of program" and give me a description, all I get is a "paused" view, much like if I had set a breakpoint. All I see is a huge stack trace, and I can press the "execute program" function several million times, moving the trace forward once line at a time. All it does is frustrate me and wear out my track pad.</p>
  
  <p>I wonder if there is any way to make use of this Stack Trace, or if I can move the trace forward to the "real" problem, or extract a human usable description from it. </p>
  
  <p>Sometimes an exception breakpoint helps to prevent a Stack Trace, but usually I feel the  debugger is letting me down. Or am I missing something and does the Stack Trace actually contain information I can use to show the problem?</p>