> On Mar 27, 2015, at 3:20 PM, Rick Mann <rm...@latencyzero.com> wrote: > > Okay, but something is still suddenly different. I didn't change my exception > configuration.
Some change in your compiled code caused a different code path through the OS's code-signing verification code, and that code path happens to involve internally throwing (and catching) a C++ exception. All you can do is shrug, really; this is just an internal implementation detail of the Security framework. As Kyle said, the workaround is to turn off C++ exception breakpoints. I find myself needing to do this any time I’m exercising code that does anything security/crypto related, or it’ll catch random throws inside Security. —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
