On Aug 25, 2016, at 16:28 , Carl Hoefs <newsli...@autonomy.caltech.edu> wrote: > > No program-related information was given in the call stack
Your scenario sounds like a genuine exception, not what I suggested earlier. However, if your app stops at an exception, and you can’t discover any useful information, try continuing execution (a few times, if necessary). Usually, the exception message hasn’t yet been displayed on the console when you break, but you’ll get it when your app goes back to the main event loop. If you’re unlucky, your app might be so messed up it never displays the exception message, and of course you lose context of the original exception if you continue, but the first time it happens you typically need to continue to find out what the exception message was. (I presume the exception message can be read by using debugger commands to display a string indirectly through a register, but I’m no good at remembering how to do things like that. For all I know, there’s a debugger command for this already.)
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
