This document explains how your Microsoft Visual C++ application can be modified to provide full debug information on the BugSplat website when it crashes.
Then Download and unzip the BugSplat software development kit for Microsoft Visual C++.
To get a feel for the BugSplat service before enabling your application, feel free to experiment with the myConsoleCrasher sample application. You can find the Visual Studio project file located in your download folder at
Run the sample application without the debugger attached to post a sample crash report to our public "Fred" database.
You may also want to browse the BugSplat Native API documentation.
Add BugSplat to your application as follows-
BugSplatRC.dllto your applications installer.
You should modify your build settings so that symbol files are created for release builds, e.g.,
Note: To get fully detailed call stacks and variable names for each crash on the BugSplat website, every time you build a release version of your application for distribution or internal testing, you should upload all
.pdb files for your product at on the Symbols Page. Better yet, use the SendPdbs application as part of your build process to automate symbol upload to BugSplat.
Test your application by forcing a crash and verifying that the BugSplat dialog appears and that crashes are posted to your BugSplat account.
Finally, make sure to check that symbol names in the call stack are resolved correctly. If they aren’t, double-check that the correct version of symbol files and all executables for your application have been uploaded on the Symbols Page.