About Doctor Dump Crash Reporting System

Doctor Dump is a free crash reporting and memory dump analyzing service. It collects, organizes and stores crash reports from your customers, gives you all necessary data to fix the bug and provides your users with solution/workaround to the problem immediately after the crash.

How it works

First of all you need to integrate the Doctor Dump crash reporting library into your Windows C++ application. After that when a crash or unhandled exception occurs it will be caught and a report about the bug will be sent to the Doctor Dump, that will analyze the report and using problem footprint (that usually is a stack trace) put it to a group of exact same issues. Similar groups caused by one reason (one buggy function can be called by different callers, so stacks will differ) form a problem that is fixing unit.
Crash report
After the crash report has been uploaded user may be directed to a customized web page about that problem where may exist some information, for example a link to a version where this bug has been fixed or some workaround. Or default page may be shown, where user can see the state of the bug and ID of his report which he can use when communicate with support. Open that page
Crash report uploaded page
In the main dashboard of your application you can see overall crash statistics. Open that page
Application main page
Each problem is a collection of similar memory dump groups and a memory dump group is a collection of the reports with same stack. Open that page
Problem main page
You can see some details about each error report. Open that page
Dump group main page
Besides stack a memory dump is available for each crash report, which can significantly help to investigate and fix a bug. Analyzing a memory dump is similar to debugging an application that was paused in a breakpoint. Difference is that you cannot continue execution and due to optimization extracting local variables is not so easy. You can analyze the memory dumps in Visual Studio exactly the same way as you debug an application. But it is recommended to use WinDbg since there are a lot of tools to dissect a dump.
Learning dump in WinDBG
You can reproduce all steps above yourself. Just run Sample Application to generate crash reports and visit Doctor Dump Sample App project under Guest account and browse the problems and crash reports.
Demo tour

Features

Here is the list of Doctor Dump crash reporting system supported features:

  • Uploads, parses and stores your crash reports
  • Provides full memory dump for difficult bugs debugging
  • Effectively groups similar reports into problems
  • It is possible to set an URL for each bug that will be opened when that report will be uploaded
  • Supports multiple applications and their versions
  • Crash statistics
  • Problems search
  • May integrate with your bug tracking system
  • Role based security model
  • Channel secured by SSL protocol
  • Effective for huge applications, millions of end users and millions of reports
  • Cloud based service - fast setup and zero maintence cost

Supported platforms

  • Microsoft Windows XP and above, native x86/x64 code, compiled with debug symbol information in .PDB or .DBG file format (Microsoft C++ Compiler, Intel C++ Compiler, MASM).
  • Managed Microsoft .NET Framework code is planned.
Integrate your application with Doctor Dump crash reporting system