On Apr 2, 2015, at 7:53 AM, Dave <[email protected]> wrote: > I did that, set to to Objective-C Exceptions only and to Break on Throw, but > it doesn’t seem to break, at least, I’ve got a crashing bug that ends up with > EXC_BAD_ACCESS in main.m, is this what you would expect?
That's a different kind of exception. It's not a language exception, it's a system exception. There's no need to set a breakpoint to stop on system exceptions. The debugger does that automatically. That's in fact what you're seeing it do. If it's attributing it to main.m, that's only because that's the first frame in the backtrace that corresponds to your source code. The stack trace should also show bunches of frames in system frameworks or libraries, although Xcode may be abbreviating it. Make sure the slider is adjusted to show you the whole thing. The fact that the exception occurred in system code doesn't mean it's the fault of that system code. It usually means that a bug in your code set up a condition such that the system code would later hit a land mine. Most often, the problem is memory management. You have over-released or under-retained some object and given/left the system a dangling pointer. Regards, Ken _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
