Features/CrashHandling

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Summary: - add client-side info)
(Handling program crashes in Fedora: whoops - fix client/server to be sub-sections of Summary)
Line 16: Line 16:
 
The plan has two parts:
 
The plan has two parts:
  
== Client ==
+
=== Client ===
 
* Create a program to catch crashing programs and write out a crash report / stack trace
 
* Create a program to catch crashing programs and write out a crash report / stack trace
 
** This should be able to produce Breakpad reports, among other output formats
 
** This should be able to produce Breakpad reports, among other output formats
Line 24: Line 24:
 
** Ignore all further crashes
 
** Ignore all further crashes
  
== Server ==
+
=== Server ===
 
* Get a Socorro server running in Fedora's infrastructure
 
* Get a Socorro server running in Fedora's infrastructure
 
* Point the default breakpad configuration to it (easy)
 
* Point the default breakpad configuration to it (easy)
Line 52: Line 52:
 
== Dependencies ==
 
== Dependencies ==
  
1. None that aren't in Fedora client side. 
+
# Need to package the socorro server
2. Need to package the socorro server
+
  
 
== Details ==
 
== Details ==
Line 62: Line 61:
 
== User Experience ==
 
== User Experience ==
  
A program crashes.  We display a dialog or notification that the  
+
A program crashes.  We display a dialog or notification that the program has crashed and save a useful stack trace to a well-known location.
  
 
== Contingency plan ==
 
== Contingency plan ==

Revision as of 20:12, 31 October 2008

Contents

Handling program crashes in Fedora

Summary

As of about Fedora 6, packages no longer include the "debuginfo" data necessary for local crash handlers to get a useful stack trace. See: http://fedoraproject.org/wiki/Packaging/Debuginfo and http://fedoraproject.org/wiki/StackTraces

What we want is a system that gets information about the crash to developers in a form with complete stack trace data. There are several options for this. First, the Apport system developed by Ubuntu. See the old Features/Apport feature page.

A discussion on fedora-devel-list came to the conclusion that the Apport system as designed won't work for Fedora because it sends the complete core dump over the network.

Another option (currently used by GNOME upstream) is Breakpad and Socorro.

The plan has two parts:

Client

  • Create a program to catch crashing programs and write out a crash report / stack trace
    • This should be able to produce Breakpad reports, among other output formats
  • Notify the user when a program crashes, and allow them to
    • Save the crash data and create a report
    • Ignore further crashes of that program
    • Ignore all further crashes

Server

  • Get a Socorro server running in Fedora's infrastructure
  • Point the default breakpad configuration to it (easy)

Owner

  • Name: [none currently]

Current status

Usage cases / rationale

  • See summary

Benefit to Fedora

  • See summary

Scope

Requires running a new server in the Fedora infrastructure.

Testing

Cause a program to crash and get a report submitted to Socorro. Test that socorro correctly retraces it and gets enough information for a developer to identify the problem.

Dependencies

  1. Need to package the socorro server

Details

Optional

User Experience

A program crashes. We display a dialog or notification that the program has crashed and save a useful stack trace to a well-known location.

Contingency plan

If this plan fails for some unforseen reason, we can reinvestigate other options such as Apport.

Documentation

None needed.

Release Notes

We will want to explain to developers of Free programs how to find crash dumps.

Comments