Getting Started with Microsoft Visual C++ 2008 (9.0)


On this page, we will show you in a few simple steps how your application can be modified to provide full debug information on the BugSplat website when it crashes. To get a feel for the BugSplat service prior to enabling your application, feel free to experiment with the myCrasher sample application which is part of the BugSplat software development kit that can be downloaded by registered users.


Enabling your application with BugSplat technology:

First, make sure you have completed the following checklist:

  1. Register as a new BugSplat user.
  2. Validate your email address using the BugSplat welcome email that was sent to you when you registered. (If you don't see the email, check your junk mail folder.)
  3. Login using your email address.
  4. Download and unzip the BugSplat software development kit for Microsoft Visual C++ 2008 (9.0).

Creating defect reports using your own application

Add BugSplat to your application as follows:

  • Include "BugSplat.h".
  • Create an instance of MiniDmpSender following the example in myCrasher. The MiniDmpSender constructor requires three parameters: BugSplat database, application name and version. The BugSplat database is created and selected on the Manage Databases page. Typically, you will create a new database for each major release of your product. You supply application name and version to match your product release. These must be used when uploading symbol files for your application.
  • Link your application to "BugSplat.lib".
  • Add "BsSndRpt.exe", "BugSplat.dll", "BugSplatRC.dll" and the "DBGHELP.dll" provided to your applications installer.
Note that you should modify your build settings so that symbol files are created for Release builds, e.g:

   Build Settings

Note in order 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

  1. Create a zip file containing all the .exe, .dll, and .pdb files for your product.
  2. Upload this zip file at Symbol Management or better yet use the SendPdbs application as part of your build process to automate symbol upload to BugSplat.


Test your application

The final step is to test your application by forcing a crash. Verify that the BugSplat dialog appears and that crashes are posted to your BugSplat account. 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 symbol management page.


Please contact us with any questions or problems you have - we want to help!