We've given up reading map files since we found ExOnHook from Per Larsen
(Turbo Power ).
Once it is linked in, it generates a trace of the stack frames whenever an
exception occurs, but only if the application is not running in the IDE. If
the exception does not get handled explicitly, it dumps the call stack into
a file. Then you parse this file using a parser which interprets the map
file, and you get a log of all of your unhandled exceptions (hopefully only
a few), complete with a call stack for each one.
It costs US$69, and you can download a fully functional demo (with nag
screen)
http://home.turbopower.com/~perl/exhook.htm
We had a couple of hard to reproduce exceptions which we'd almost given up
on and ExOnHook helped us nail them.
We had a play with another utility called DebugMapper or something, but it
doesn't compare to ExOnHook
In a word ( two actually), BUY IT.
If nothing else, it gives you something to do (a file to parse ) when an
unhandled exception happens in front of someone, so you don't feel quite so
useless.
I hope this helps
Paul
PS There was an article in The Delphi Magazine, Oct 99 which discussed
exception stack tracing.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
