Abstract

There is a gap between the information available at the time of a software failure and the information actually shipped to developers in the corresponding bug report. As a result, identifying the cause of the bug based on this bug report is often difficult. To close this gap, we propose bug fingerprints an augmentation of classic automated bug reports with runtime information about how the reported bug occurred in production.

Details

Actions