Testing Native crashes with the sample application ‘myConsoleCrasher’

Before you enable your native Windows application with BugSplat technology, you may want to take a moment to experiment with our myConsoleCrasher sample application.

First, login to BugSplat with user name 'fred@bugsplat.com' and password ‘Flintstone’.

All of the crash reports in the fred@bugsplat.com account are actual crashes created with our sample applications. Reports from myConsoleCrasher are mixed in with reports from other applications on the Crashes page.

To view just the myConsoleCrasher crashes, filter using the drop-down menu in the header of the application column:

Next, download the BugSplat Microsoft Windows Native SDK from the Downloads page and open the myConsoleCrasher Visual Studio project in the samples folder.

Rebuild the project, and run it outside of the Visual Studio debugger (ctrl-F5). This is important since the debugger interferes with the BugSplat library’s exception handling. You should see a dialog such as that shown below (make sure to type something describing the crash so that you can identify it on the website):

Click the Send Error Report button and voilà! The report will be sent! On the BugSplat website while logged in to the 'fred@bugsplat.com' account, look for the crash report with the description you entered.

You also can easily modify myConsoleCrasher so that crash reports are sent to a database in your account instead. Just modify the following line in myConsoleCrasher.cpp, changing ‘fred@bugsplat.com’ to the name of your database:

mpSender = new MiniDmpSender(L"Fred", L"myConsoleCrasher", L"1.0", NULL);

Finally, experiment with other features of the library by examining the myConsoleCrasher source code and supplying different command-line arguments.