On Jul 30, 2013, at 3:13 AM, Oleg Krupnov <oleg.krup...@gmail.com> wrote:
> I'd disagree. This thread has already crashed and its exception was > not caught, and so the thread is about to be terminated with or > without my intervention. Killing it myself would hardly produce any > side effects. I just want to prevent the entire app from termination > and so far it seems darn impossible. The entire app is about to terminated precisely because the thread is in an unknown corrupt state, likely having corrupted the heap or stack, and possibly holding a crucial lock or other resource, so continuing is completely unreliable. If your goal is to present a dialog to the user and ask that the user send diagnostic info to you, use an external process monitoring your logs and/or crash reports. (And don't try to log after an unhanded exception; log info before.) -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice _______________________________________________ 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
