Re: error report for MY apps?
- From: "Stuart Irving" <spam@xxxxxxxxxxxxxxxx>
- Date: Tue, 4 Apr 2006 15:05:15 +0100
If you're running under Windows XP, consider converting the exception into a
null pointer dereference in the catch handler:
catch(...) { // now we're really stuffed
int * p = 0;
*p = 22;
This has the advantage over an ordinary crash that you will get one of those
special OS-supplied dialogs, that asks permission to send log details back
to Microsoft. Naive users will interpret this as a Windows fault, and will
direct their bile Redmondwards.
Of course, all the above techniques can be combined in fresh and original
ways. Never be afraid to experiment.
The primary duty of an exception handler is to get the error out of the lap
of the programmer and into the surprised face of the user. Provided you keep
this cardinal rule in mind, you can't go far wrong.
[from The Register]
;)
"sklett" <sklett@xxxxxxxxxxxx> wrote in message
news:eMNljx9VGHA.1764@xxxxxxxxxxxxxxxxxxxxxxx
You know when an application crashes and it will popup that dialog that
asks you if you want to send an error report? What is that called? I
want to add that to my applications, but I'm not find what it's called so
I can learn more.
Thanks for any tips,
Steve
.
- References:
- error report for MY apps?
- From: sklett
- error report for MY apps?
- Prev by Date: Re: DataGridView bound to List<T>
- Next by Date: Re: System.Net.Sockets.Socket threw an exception
- Previous by thread: Re: error report for MY apps?
- Next by thread: Icon in ImageList back to a USABLE Icon format...
- Index(es):
Relevant Pages
|
