Features/CrashHandling

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(move to new category naming)
(Fix Breakpad URL.)
Line 12: Line 12:
 
[http://www.redhat.com/archives/rhl-devel-list/2008-June/msg01250.html 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.
 
[http://www.redhat.com/archives/rhl-devel-list/2008-June/msg01250.html 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 [http://code.google.com/p/breakpad/ Breakpad] and [http://code.google.com/p/socorro/ Socorro].
+
Another option (currently used by GNOME upstream) is [http://code.google.com/p/google-breakpad/ Breakpad] and [http://code.google.com/p/socorro/ Socorro].
  
 
The plan is thus:
 
The plan is thus:

Revision as of 08:56, 12 August 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 is thus:

  • Get a Socorro server running in Fedora
  • Point the default breakpad configuration to it

The hard part is the first.

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. None that aren't in Fedora client side. 2. Need to package the socorro server

Details

Optional

User Experience

A program crashes. We display a dialog or notification that the

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