When the debugger stops, go to "Debug Navigator" and make sure the slider at the bottom is on the right.
Scan your eye down from the point where the exception is thrown, and you should end up with your own code. Click on the corresponding method / function name and the code will open in the editor.


If you do not see any of your own methods in the stack trace, the exception can be performSelector through a call to performSelector -style, in which case the stack trace will disappear. If so, you can get better information by adding an βOn Throwβ exception exception point. First, switch to the breakpoint navigator:

Then click on the plus and select "Add Exception Control Point ..."

Create a breakpoint "On Throw":

This will stop the debugger in the exact place when the exception is thrown and you get the best stack trace. It is a good idea that an exception-throwing time like this is constantly turned on, although sometimes you get internal exceptions from Apple code (for example, when using QLPreviewController, MPMoviePlayerController).
Mike Weller May 08 '12 at 3:19 p.m. 2012-05-08 15:19
source share