🚀 go-pugleaf

In message <B92F4E8E.38BA%jbotwick@nc.rr.com>, Jason Botwick 
<jbotwick@nc.rr.com> writes
>What's the best way to diagnose the cause of crashes that occur on software
>that you have deployed to a user? When I was writing UNIX applications, we
>could always examine the core dump. Is there some analogue under Windows?
>Are there some tools that you can use to save the state of an application
>when it crashes?
>

1) Dr Watson log.

2) Always create a map file (including lines /MAPINFO:LINES) for each 
DLL you ship and keep them safe.

3) If you visit http://www.objmedia.demon.co.uk (go to software) and get 
the MapFileDLL and MapFileExplorer projects you will be able to load a 
map file and then type in the DLL load address and the crash address and 
the MapFileExplorer will tell you, to the nearest line where the crash 
happened. The map file loads quickly, but populating the tree control 
takes some time for large (3MB) map files (ie: 30 seconds or so).

You may also like to use a professional tool to analyse your memory 
related problems. http://www.softwareverify.com

Regards

Stephen
-- 
Stephen Kellett         http://www.objmedia.demon.co.uk
Object Media Limited    C++/Java/Windows NT/Unix/X Windows/Multimedia
If you are suffering from RSI, contact me for advice.
Unsolicited email from spam merchants not welcome.