Hi Ken, > Let the app crash. Let the CrashReporter tell the user that it crashed. If > you want to receive the crash report yourself, use an external watchdog > process or collect the crash report file on next launch.
I'd agree that this approach technically is more correct. One downside of it though is that the user should launch the crashed app at least one more time. Hopefully, it's not going to be a crash on first launch followed by immediate trashing of the app :) So it boils down to these questions: 1. What is the correct way of terminating the app if the exception happens in the main thread? I need the system Crash Reporter to save the context and stack trace of the original problem, not of some exception handler. 2. Will it work in sandboxed mode? The folder with crash reports may appear unaccessible. P.S. It dawned at me that I could relaunch another instance of the app (using a shell script) before my app terminates, in this way relying on the user to do this is not needed. Thanks. _______________________________________________ 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
