Categorizing and reporting crashes

Jan 7, 2011 at 2:03 PM
Edited Jan 7, 2011 at 2:53 PM

This project is intended to provide the ability to create cases in Fogbugz - a defect tracking tool.  One of the capabilities of Fogbugz is to correlate the "same" defect from multiple sources - rather than create new cases it will append or ignore additional information based on preferences set in the cases. 

This correlation does not come "for free".  The developer must determine which defects are "the same". 

The following two URLs discuss "bucketing"/correlation and are good background. 

"Debugging in the (Very) Large: Ten Years of Implementation and Experience" - from Microsoft

Bug Buddy

Additionally, these StackOverflow questions are related to the subject matter:

How does Microsoft generate the Event ID for winqual events?

How do I get a string description of a Win32 crash while in Top level filter

What is a good way to create a string for crash reporting Win32 C++ that reflects the cause of the crash?

Some additional liks that may be of use - especially for Windows developers:

CrashRpt library

StackWalk code

At this time the implementation of creating a "scout" description for Fogbugz is left as an exercise for the reader, but we hope to update this page with specific code to provide a reasonable first step/implementation of a "bucketing" algorithm.

We encourage feedback, comments and suggestions for solving this either generally or for specific cases.