Priority

UbuntuDownUnder/BOFs/UbuntuDevelopment/AutomatedProblemReports

Status

• Created: Date(2005-04-23T05:46:42Z) by MattZimmermanBR

• Priority: LowPriorityBR

• People: NeedsLead, NeedsSecondBR

• Contributors: MattZimmermanBR

• Interested: MartinPitt, LaMontJones, MichaelVogt, SebastienBacherBR

• Status: BrainDump, BreezyGoal, UduBof, DistroSpecificationBR

• Branch: BR

• Malone Bug: BR

• Packages: BR

• Depends: BR

• UduSessions: 1, 4, 8, etc BR

Introduction

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

Rationale

Scope and Use Cases

• 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]?

Implementation Plan

Data Preservation and Migration

Packages Affected

User Interface Requirements

Outstanding Issues

UDU BOF Agenda

• What data needs to be submitted?

  • core dump; MartinPitt: core dumps are difficult to handle since you need to have exactly the same libraries; a good stack trace is already very helpful, much smaller, and easier to handle

  • identifying information for all code involved (package versions? filenames? md5sums?)
  • additional run-time information (environment, command line arguments, user comments for reproduction)
• How should the debug symbol extraction work?
• Handling and caching of debug symbols on client
• Automated bug reporting to Malone

UDU Pre-Work

• MartinPitt already has a prototype for crash reports, see AutomatedCrashReporting