Properly uploading symbols for Windows (native and .NET).

A common stumbling block for new BugSplat users is getting symbols to upload properly for Windows (native and .NET).

To help alleviate this issue we’ve put in a helpful way to check if you’ve done this right.

To start, go to an individual crash page and click the ‘Calculate Details’ button.

 
newsymbols#1
 

Once the details load, scroll through the crash them to find a column labeled ‘Symbols’ in the modules section. When there you will see one of four different response types.

  • deferred: debugger doesn’t need the module’s exe/dll/symbols to unwind the stack.
  • file not found: debugger needs the module’s exe/dll/symbols to unwind the stack, but the exe/dll with matching debug signature cannot be located.
  • symbols not found: the debugger needs the module’s exe/dll/symbols to unwind the stack and the matching exe/dll has been located, but not the symbols.
  • pdb symbols: debugger needs the module’s exe/dll/symbols to unwind the stack and they have been loaded successfully.

To read about this in more detail see our full document –> http://www.bugsplat.com/Documents/are-my-windows-symbols-working/

Comments are closed.