Summary
If a process crashes and this crash is not picked up by Dr. Watson, a user dump is not generated or you have a hanging process and you want to save its dump.
WinDbg is able to monitor a specific process, log the information and save it so it can be analyzed.
Procedure
1. Install Debugging Tools for Windows on the server (WinDbg will be installed automatically).
2. Launch the application in a session.
3. Launch WinDbg within the same session and press F6, a list with all available processes is shown. Select the process in question and wait until you see “DbgBreakPoint:” in the command window of WinDbg.
4. If you have a hanging process and you want to save the dump now go to step #6.
5. Type g on the command line of WinDbg.
6. Reproduce the crash (in WinDbg further information is listed).
7. On the command line of WinDbg type .dump /f filename to save that information to a file. The default location is \Program Files\Debugging Tools for Windows\.
8. Create a zip file containing the recently created memory dump and the symbols of the application and send it for analysis.
NOTE: On some operating systems such as Windows 2003, Windows XP and later you can use /ma switch instead of /f switch to save additional debugging information such as handle data, and thread time information.
For 32-bit applications running on 64-bit Windows (shown as *32 in Task Manager) you must use WinDbg.exe from the 32-bit Debugging Tools for Windows.
More Information
Debugging Tools for Windows is available from Microsoft and can be downloaded from the following link: http://www.microsoft.com/whdc/devtools/debugging/default.mspx
