AutomatedProblemReports

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2005-04-11 11:28:45 →
Size: 1149
Editor: pD9E85D28
Comment: added AutomatedCrashReporting link
← Revision 4 as of 2005-04-11 15:19:07 → ⇥
Size: 1074
Editor: pD9E85D28
Comment: updated AutomatedCrashReporting link
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:
 * MartinPitt already has a prototype for crash reports, see [wiki:Self:UbuntuDownUnder/BOFs/UbuntuDevelopment/AutomatedCrashReporting AutomatedCrashReporting]  * 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)