Crash Dump Analysis
This guide discusses how to analyze crash dump files in Visual Studio.
If Rhino crashes, two files are created on the user’s desktop: RhinoCrashDump.dmp and RhinoCrashDump.3dm. The .3DM file is Rhino’s last ditch effort to save the model. The .DMP file can be used in Visual Studio to find the place in the source code where a Rhino plugin crashed.
Before you can analyze crashes, you’ll need to set up visual studio to help you get symbols.
- Enable Symbol Servers
- Open Visual Studio
- From the Tools menu, click Options
- Select the Debugging > Symbols tab
- In the Symbol file (.pdb) locations box, add:
- Optionally add these symbol servers if you need symbols for OpenGL driver related crashes:
- In the Cache symbols in this directory folder enter a folder where Visual Studio will cache symbols. Depending on the number of crashes you debug, this folder can get quite large.
- Under Automatically load symbols for: select Load all modules, unless excluded (Note that this will make debugging your project slow. To speed this up, select Load only specified modules)
- Download and extract the Zip archive containing the crash dump.
- Start Visual Studio 2017
- From the File menu, click Open
- Browse to the RhinoCrashDump.dmp file in the extracted folder
- Click Debug using mixed
- For details we’ve extracted about the crash, view the RhinoCrashDump.dmp.xml file.
Below is a sample C++ plugin that will crash Rhino. To test out crash dump analysis:
- Download and build the TestSdkCrash plugin.
- Launch Rhino and load the plugin using the
- Run the
- While the McNeel Error Reporting dialog is displayed, copy the RhinoCrashDump.dmp from the desktop to some other location, and then click Don’t Send.
- Follow the steps above to analyze the crash dump.
In order to get the most out of your crashes, you need to save the symbols and source code from each of the builds. You’ll also need to add source information into your PDB files before you store them in the symbol server.