SmartException is a utility that can be used to help
gather additional information about an application that
has crashed. |
Download SmartException from http://storage.stardock.com/files/smartexception.exe
and install it.
The default installation folder for SmartException is:
This directory is also where the .CRA and .DMP files are created.
Launch SmartException. Once it is running, you can
access it from the notification area/system tray.
When an application who's .EXE is in the configured list
crashes, a dialog appears in addition to the
Windows Error Reporting dialog (on XP). This dialog
allows you to enter what you were doing and
optionally include up to 10 images to be sent with your
After completing the dialog, an Explorer folder will
open with an ExceptionLog.zip file. Please
use your email program to send that to the email address
and subject line that SmartException
prompts you with.
The information logged will contain details of the
crash, including some system information (Please see the
privacy statement at the bottom of the page for more
details). In some cases, like Galactic
Civilizations, the zip will
also attempt to bundle additional debug files from the
application (like debug.err and your last AutoSave).
The .CRA files and the Dump files will also be
in the .zip file.
Please feel free to look over the files in the zip prior
to sending. At no time does SmartException automatically
send any information, you have to create an email and
attach the zip file.
SmartException is set by default to only report on
exceptions with Stardock applications. You can modify
\Windows\SmartEx.ini to add definitions for your own
applications and to increase the level of debug
output if requested by the developers.
SmartExeception installs to \Program Files\Stardock\SmartException
and once run under a given user will automatically
configure itself to load on startup for that user.
Adjust its settings via its icon in the system tray.
SmartException can also capture Win32 OutputDebugString
information from applications via the Debug Logger
option on its system tray icon. For more fully featured
debug output logging, you can't beat