Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
developer:crashdumpanalysis [2016/01/05]
sandy
developer:crashdumpanalysis [2016/01/05] (current)
sandy
Line 14: Line 14:
 Keep in mind you are debugging optimized code. Some values of local variables (like loop counters and frequently used doubles) are kept in CPU registers and cannot be viewed in a watch window. Keep in mind you are debugging optimized code. Some values of local variables (like loop counters and frequently used doubles) are kept in CPU registers and cannot be viewed in a watch window.
  
-If you read a RhinoCrashDump.dmp file in Notepad.exe and search for "​RHINOCRASHINFO"​ you will find a block of text that looks like the following:+If you read a RhinoCrashDump.dmp file in Notepad.exe and search for "​RHINOCRASHINFO"​ you will find a block of text like the following:
  
    <​RHINOCRASHINFO>​    <​RHINOCRASHINFO>​
Line 24: Line 24:
 If the crash happens in a command that is in a plug-in, the name of the plug-in'​s .RHP file is in <​EXECUTABLE FILENAME>​ and the id is in <​EXECUTABLE UUID>. If the crash happens in a command that is in a plug-in, the name of the plug-in'​s .RHP file is in <​EXECUTABLE FILENAME>​ and the id is in <​EXECUTABLE UUID>.
  
-<BUILD DATE> and <BUILD TIME> are the date and time the .cpp file that contains the crash dump exception ​handing ​code was compiled.+<BUILD DATE> and <BUILD TIME> are the date and time the .cpp file that contains the crash dump exception ​handling ​code was compiled.
  
 =====Analyzing a crash===== =====Analyzing a crash=====
Line 36: Line 36:
    ​2007-07-03 - Rhino 4.0 SR1    ​2007-07-03 - Rhino 4.0 SR1
  
-====Step 2. Get the build of Rhino that has crashed====+====Step 2. Get the build of Rhino that crashed====
 To analyze the crash dump file, you need the build of Rhino on your system that produced the crash dump. If you do not have the same build, download it from the Rhino web site. To analyze the crash dump file, you need the build of Rhino on your system that produced the crash dump. If you do not have the same build, download it from the Rhino web site.
  
Line 44: Line 44:
    ​C:​\Program Files\Rhinoceros 4.0\System    ​C:​\Program Files\Rhinoceros 4.0\System
  
-Over the life of your plug-in, you are likely to see many crashes. So do yourself a big favor and rename the RhinoCrashDump.dmp file something descriptive.+Over your plug-in's life, you are likely to see many crashes. So do yourself a big favor and rename the RhinoCrashDump.dmp file something descriptive.
  
 Also, copy your plug-in'​s release .RHP and .PDB files into the same folder. ​ Also, copy your plug-in'​s release .RHP and .PDB files into the same folder. ​
Line 66: Line 66:
 The Microsoft Symbol Server is built by using the SymSrv technology (SymSrv.dll) provided with the Debugging Tools for Windows package. SymSrv builds a local symbol cache for fast, automatic symbol resolution. The Microsoft Symbol Server is built by using the SymSrv technology (SymSrv.dll) provided with the Debugging Tools for Windows package. SymSrv builds a local symbol cache for fast, automatic symbol resolution.
  
-You can use the symbol server to allow Visual Studio to automatically download the proper Microsoft symbols for debugging your Visual Studio project. To allow Visual Studio to use the Microsoft Symbol Server, select **Tools->​Options** and fill in the information ​as listed below.+You can use the symbol server to allow Visual Studio to automatically download the proper Microsoft symbols for debugging your Visual Studio project. To allow Visual Studio to use the Microsoft Symbol Server, select **Tools->​Options** and fill in the information listed below.
  
 {{:​legacy:​en:​symsvr.png}} {{:​legacy:​en:​symsvr.png}}
developer/crashdumpanalysis.txt ยท Last modified: 2016/01/05 by sandy