> On Sep 25, 2013, at 10:00 AM, Jerry Krinock <[email protected]> wrote:
> > >> On 2013 Sep 25, at 09:39, Kyle Sluder <[email protected]> wrote: >> >> That looks like a C++ exception. What happens if you edit the breakpoint to >> only break on ObjC exceptions? > > Thanks, Kyle. Good guess. Indeed, if I edit the breakpoint and change the > popup from "All" to "Objective-C", then it does not break when I try to > reproduce. > > What do we think of that? I'd hate to conclude that Cocoa's built-in C++ > Exceptions are not worthy of attention. Please note that the breakpoint traps on exception *throw*. It is perfectly valid—daresay common—for C++ code to throw and catch exceptions as a normal matter of course. Uncaught exceptions of all varieties will still trigger the uncaught exception handler. Whether an exception gets that far is another matter. > > By the way, I actually need to hit the "Continue" button in Xcode three > times, with smaller call stacks. Apparently three functions in that stack > are raising an exception. It’s probably being caught and re-thrown. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
