Testing Windows Native C++ 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
All of the crash reports in the
[email protected]account are actual crashes created with our sample applications. Reports from
myConsoleCrasherare mixed in with reports from other applications on the Crashes page.
To view just the
myConsoleCrashercrashes, filter using the drop-down menu in the header of the application column:
Search for Crashes Containing MyConsoleCrasher
Next, download the BugSplat Microsoft Windows Native C++ SDK from the Downloads page. Once the SDK has downloaded, right click
BugSplatNative.zipand choose and
Extract All. Failing to extract the contents from the zip will result in numerous build failures. Once the contents of
BugSplatNative.ziphave been extracted navigate to the
samplesfolder and open the
myConsoleCrasher.vcxprojfile with Visual Studio.
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):
BugSplat Crash Dialog
Send Error Reportbutton and voilà! The report will be sent! On the BugSplat website while logged in to the
[email protected]account, look for the crash report with the description you entered.
You also can easily modify
myConsoleCrasherso that crash reports are sent to a database in your account instead. Just modify the following line in
Fredto 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
myConsoleCrashersource code and supplying different command-line arguments.