Testing the sample application 'myCrasher'

Before you enable your application with BugSplat technology, you may want to take a moment to examine the defect reports created by one of our sample applications. To do this, login to BugSplat with user name 'Fred' and password 'Flintstone'. All the defect reports in the Fred account are actual crashes created with our sample applications.

The instructions on this page discuss how to use the example C++ program myCrasher.exe to post crash reports to BugSplat. The process for our other sample programs is similar. You can find myCrasher.exe in the BugSplat unmanaged download libraries (available to registered users).

Launch the sample program myCrasher.exe without making any changes. Many of the buttons on the dialog will cause a crash. When a crash occurs, fill out the requested information and select 'Send'. You can verify that crash report was created by logging into the Bugsplat website with user 'Fred' and password 'Flintstone' and selecting 'All Crash Reports'. Look for a recent crash post that has the crash description you created.

You can also take a look in the Event Viewer under Control Panel, Administrative Tools and locate a recent BugSplat Application event
   

Modifying the sample application 'myCrasher' to use your BugSplat account

Next,we will change the sample app so that crash reports are sent to your user id.
In myCrasherDlg.cpp search for the following line:
   MiniDmpSender sender("Fred", "FredsApp", "2.0", "English Version");

Make the following changes:

• Modify the database name string "Fred" to your BugSplat database. The BugSplat database is created and selected on the Manage Databases page.
• Change the application name "FredsApp" to a name of your choice (this is an arbitrary string, used to distinguish your applications across crash reports.
• Change the version from "2.0" to a string of your choice. Again this is arbitrary, but would typically match the version and build string of your application.
• Change the Application ID from "English Version"to a string of your choice. This is optional and arbitrary, and can be used to distinguish between different uses for a single compiled version of your application.
  For example, you could use it to indicate which set of localized resources are in use.

Compile and link the myCrasher project.
Make sure you switch to the Release configuration before building.

In order to get good debugging information, you should also create a zip file containing all PDB files and the myCrasher executable and upload the zip to your acccount as follows:

1. Login to BugSplat with your user id.
2. Upload the zip file from the previous step using Symbol Management.
   Make sure the application name and version string that you specify match the changes you made to myCrasherDlg.cpp earlier.

Next, Launch mycrasher.exe (not from the debugger!) and select a crash button.
Fill in the requested information in the crash dialog and select "Send Report"

   

To verify that the report was sent, log into BugSplat and verify the defect was recorded.