Re: Uncaught exceptions not terminating my app
Re: Uncaught exceptions not terminating my app
- Subject: Re: Uncaught exceptions not terminating my app
- From: "Paul Sanders" <email@hidden>
- Date: Thu, 28 Jan 2010 08:10:38 -0000
If you don't crash the app, you don't get the stack trace. No
stack trace = no clue about what went wrong. And we do offer to
save the user's work (in the NSExceptionHandler delegate) before
we bail out.
And the idea, obviously, is to fix the crashes in the next
maintenance release. We have a regular release cycle. My
experience is that users don't mind a few problems if they get
prompt support and know that you are on the case, and if you are
in a position to figure out what caused the crash you can often
suggest a workaround, pro-tem.
Paul Sanders.
----- Original Message -----
From: "Jens Alfke" <email@hidden>
To: "Paul Sanders" <email@hidden>
Cc: "Ken Thomases" <email@hidden>;
<email@hidden>
Sent: Wednesday, January 27, 2010 7:27 PM
Subject: Re: Uncaught exceptions not terminating my app
On Jan 27, 2010, at 11:01 AM, Paul Sanders wrote:
> My basic tenet is that I want to catch unexpected exceptions
> and
> terminate my app in a way that produces a crash report
> containing a
> proper stack trace.
As a developer I understand your desire; but as a user, I would
rather
have your app pop up an error alert, than suddenly crash and
lose my
unsaved work. (In my experience, most uncaught exceptions will
allow
the app to keep limping along afterwards, enough to show an
alert and
let the user save and quit.)
It wouldn't be too hard to integrate the unexpected-error alert
with
UKCrashReporter so that it can send the backtrace to you; then
you get
the best of both worlds.
—Jens
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden