On Oct 14, 2011, at 4:45 PM, Quincey Morris wrote: > As an aside, TBH, I've never seen any evidence that uncaught (by my code) > exceptions lead to the process being killed. Typically, the process just > continues after logging a message. Maybe that's because I'm typically running > from Xcode so via the debugger, but I don't know that exceptions (like a > NSArray index out of bounds exception) kill the app on customer Macs either.
Raising an exception only kills the process if there is no handler (@catch block) at all on the thread’s stack. Most of the time you’re running on a thread with a runloop, and the runloop has an exception handler. But if you spawn a new thread it won’t have any exception handler, so an uncaught exception will crash. —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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
