[DUG] exception handling

[Paul Heinz]

Hi Ross

 

You are probably best considering some form of enhanced exception
reporting. They allow showing not just the exception but also a full
stacktrace (and more if desired) and allow these to be emailed to you.
EurekaLog  and madExcept (which we use) both have good reputations but
are admittedly commercial products that you'd need to pay for.

The JEDI library has basic but workable exception reporting support and
is freely available under an open source license. In fact, we're
currently using the JEDI support in our 64-bit builds until such time as
madExcept finalises it's 64-bit support. I think EurekaLog already has
64-bit support in it's current beta build. 

 

Cheers,

  Paul.

 

From: delphi-bounces at listserver.123.net.nz
[mailto:delphi-bounces at listserver.123.net.nz] On Behalf Of Ross Levis
Sent: Tuesday, 24 April 2012 3:59 p.m.
To: 'NZ Borland Developers Group - Delphi List'
Subject: [DUG] exception handling

 

This is likely a simple question but I've never dealt with it before.

 

Way back in Windows 98 days if an exception was raised, the description
of the exception was displayed in a message box.  These days in XP,
Vista, 7, you get options to send reports to Microsoft or other obscure
dialogs which don't even mention anywhere what exception occurred, even
if you click  the "More information" link.

 

Is there a simple way to get all exceptions to display a message box
again before terminating?  It would make life so much simpler when
debugging with users.

 

Cheers,
Ross.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20120424/dc1845f2/attachment.html