On Jan 28, 2010, at 12:10 AM, Paul Sanders wrote: > If you don't crash the app, you don't get the stack trace. No > stack trace = no clue about what went wrong.
That's why I said the error alert should include the same "Report" button as the crash report would. > And we do offer to > save the user's work (in the NSExceptionHandler delegate) before > we bail out. That's fairly dangerous. At that point you have no idea what's on the stack or what operations are halfway done. If you're doing inside a half-completed AppKit or HLTB call, putting up any UI creates re-entrant calls. If you're inside your own code, you're calling yourself re-entrantly when you save. It's safer to save away the exception info, let the stack unwind fully, and then on the next runloop cycle put up the alert: http://bitbucket.org/snej/myutilities/src/tip/ExceptionUtils.m —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
