I doubt you are missing something & you may be right that maybe NSExceptionHandler can be used (with the right mask). The only real input I have on this matter is that I consider it fragile to fail if an Apple framework throws an exception internally. You'll need to be able to detect exceptions are "thrown *and* not caught" by the frameworks.
I have not need to do this, and I can therefore not offer a solution that I know works. Jesper On Feb 2, 2010, at 2:37 PM, Kyle Sluder wrote: > On Tue, Feb 2, 2010 at 2:28 PM, Jesper Storm Bache <jsba...@adobe.com> wrote: >> Did you try: >> NSException.h: >> void NSSetUncaughtExceptionHandler(NSUncaughtExceptionHandler *); > > I might be missing something here, but why would this be usable and > NSExceptionHandler not? NSExceptionHandler is documented to work by > installing an uncaught exception handler using this function. > > --Kyle Sluder _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
