Usual Introductory Blah
About a year ago I wanted to dump Microsoft Visual C++ in favour of MinGW, since I’d have really liked to use ‘modern’ C++11 features.
However, the promises of out-of-band compiler updates with better C++11 support and the fact that it is easy to create minidumps via dbghelp.dll’s functionality and debug them with windbg were enough to delay this move.
With the announcement of MSVC 2013 and its - still - lackluster support for C++11 I gave in. However losing the debugging support for crashdumps really hurts. But every search on the web only turned up other unsuccessful inquiries about a working post-mortem debug facility with MinGW.
The only sane way to create crash-dumps under Windows is to use dbghelp.dll’s Minidump functionality. This minidump can then be loaded with windbg (or Visual Studio). However, both applications need a PDB file to show useful information (unless assembly and memory addresses instead of function names is sufficiently informative for you). A file, gcc does not create, since it stores its debug information in DWARF format. A format neither of those programs can handle.
So how about the other side? gdb can of course handle DWARF files. But it can not load minidump files.
Luckily(?) the ecosystem of the D programming language faced a similar problem. So that is where the solution can be found: cv2pdb, which can not only convert CodeView files to PDB, but also the DWARFen ones!
Create the Debug Info
- Compile/link your project with debug information (
- Use cv2pdb to convert the DWARF debug info into PDB format (
cv2pdb -C program.exe)
- Strip the executable from any debug info (
strip -g program.exe)
- Distribute the executable and keep the PDB file
The PDB file and the executable cannot be matched automatically based on their checksum, since the strip changed it. So you need an out-of-band way to match the correct files.
The way I do it: on an actual crash I create the minidump and pack it together with the logfile, which contains the application’s version number, into a zip or tar file before sending it off. That way I can match the minidump to the correct PDB file.
Since the executable was stripped of any link to the PDB file windbg tries to load a generic
image00400000.pdb file (or
image00000000`00400000.pdb for 64bit executables).
So make sure that is the PDB’s file name.
I for one just archive the PDB files named this way and put them in a directory for each version.
- The directory containing this file needs to be added to windbg’s symbol search path. (
- Further more, since the PDB file and executable cannot be matched
.symoptneeds to be changed, to include
SYMOPT_LOAD_ANYTHING). Combined with the default symopts this is
- And finally the actual dump file needs to be specified with the
- While I’m at it: I also add
-gto skip the initial breakpoint.
All in all I end up with a command line like this to start windbg to do post-mortem debugging with a minidump:
windbg -sflags 0x80030377 -g -y <directory_containing_correct_pdb_file> -z <path_to_dumpfile> <path_of_correct_executable>