AutomatedProblemReports

Differences between revisions 2 and 5 (spanning 3 versions)
⇤ ← Revision 2 as of 2005-04-10 23:39:26 →
Size: 988
Editor: ca-studio-bsr1o-251
Comment: merge zwiki stuff
← Revision 5 as of 2005-04-12 08:01:53 → ⇥
Size: 1094
Editor: ANancy-151-1-15-174
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * SebastienBacher
Line 29: Line 30:
 * MartinPitt already has a prototype for crash reports, see AutomatedCrashReporting

People

Goal

Streamline the process of collecting data for common end-user problems, so that they can be prioritized and addressed

Requirements

  • When a program crashes, send a report (with an absolute minimum of user interaction)
  • Extract and store debug symbols from standard builds, and store them in a centralized repository for use in analyzing these reports
  • When a package installation, removal or upgrade fails, send a report (with an absolute minimum of user interaction)
  • When a kernel panic/oops/etc. occurs, send a report (with an absolute minimum of user interaction)

  • [http://www.cs.wisc.edu/cbi/ Cooperative bug isolation]?

Agenda

  • What data needs to be submitted?
    • core dump
    • identifying information for all code involved (package versions? filenames? md5sums?)
  • How should the debug symbol extraction work?
  • Automated bug reporting to Malone

Pre-Work

AutomatedProblemReports (last edited 2008-08-06 16:26:25 by localhost)