AutomatedProblemReports

Differences between revisions 1 and 6 (spanning 5 versions)
⇤ ← Revision 1 as of 2005-04-04 18:03:03 →
Size: 889
Editor: ca-studio-bsr1o-251
Comment:
← Revision 6 as of 2005-04-19 00:33:38 → ⇥
Size: 1134
Editor: 150
Comment: pri
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Priority =

NeedPriorityAssigned
Line 6: Line 10:
 * SebastienBacher
Line 18: Line 23:
 * [http://www.cs.wisc.edu/cbi/ Cooperative bug isolation]?
Line 25: Line 31:
 * Automated bug reporting to Malone
Line 27: Line 34:
 * MartinPitt already has a prototype for crash reports, see AutomatedCrashReporting

Priority

NeedPriorityAssigned

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)