Features/ABRT

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
m (Fix the project name on text)
(Documentation: fix redlink, clean up HTML comment)
 
Line 81: Line 81:
  
 
== Documentation ==
 
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
 
* [https://fedorahosted.org/abrt/wiki abrt home page]
 
* [https://fedorahosted.org/abrt/wiki abrt home page]
 
* Setup and test docs from the test days:
 
* Setup and test docs from the test days:
 
** [[QA/Test_Days/2009-02-26]]
 
** [[QA/Test_Days/2009-02-26]]
** [[QA/Test_Days/2009-08-20]]
+
** [[Test Day:2009-08-20 ABRT]]
 
* [[http://fedoraproject.org/w/uploads/a/ab/ABRT.odp ABRT FUDCon Berlin 2009 presentation]]
 
* [[http://fedoraproject.org/w/uploads/a/ab/ABRT.odp ABRT FUDCon Berlin 2009 presentation]]
  

Latest revision as of 21:27, 7 October 2009

Contents

[edit] ABRT

IMPORTANT NOTE!! -> THIS PROJECT HAS BEEN RENAMED TO ABRT - Automatic Bug Reporting Tool (previously known as CrashCatcher)

[edit] Summary

The tool to help non-power users with bug reporting, making it as easy as a few mouse clicks.

[edit] Owner

  • email: zprikryl@redhat.com, jmoskovc@redhat.com

[edit] Current status

  • Targeted release: Fedora 11
  • Last updated: 2009-03-05
  • Percentage of completion: 100%

[edit] Detailed Description

This feature semi-automatically provides information about defects and crashes on user system. It collects necessary data about the crash, generates a report with all information and based on user interaction sends it to some bug reporting system. The goal is to have this tool heavily plugin-able - so it can be used for any compiled/scripting language and bug reporting system (trac, BZ, 3rd party bug reporting tool ...)

[edit] Benefit to Fedora

Ease of bug reporting and quick response from maintainers based on info from ABRT should make Fedora more stable and thus more attractive for users.

[edit] Scope

what has to be done:

  • pluginable architecture
  • daemon for detecting crashes
  • authentication system
  • system detecting if binary belongs to our package (PackageKit support)
  • add-ons for languages
  • plugins for reporters, databases of crashes, specific applications
  • GUI and TUI

It shouldn't affect any part of Fedora, it's desing allows to easilly disable or remove this application completelly.

[edit] How To Test

  • Install ABRT with C/C++ language plugin.
  • Run some app. This app has to be written in C or C++.
  • kill -s SIGSEGV <pid of app>
  • See if ABRT detects it.

[edit] User Experience

  • If an application crashes, the user is notified by a trayicon (or a message in a log) and a simple wizard will act as a guide through the bug reporting process. All required information is gathered automatically so bug reporting should be easy even for less experienced users.

[edit] Dependencies

  • dbus
  • gtk2
  • PackageKit
  • PolicyKit
  • Archer
  • sqlite
  • gtkmm
  • Python
  • glade

[edit] Contingency Plan

None necessary, revert to previous release behaviour :)

[edit] Documentation

[edit] Release Notes

There is no simple tool for debugging programs and reporting bugs in Fedora and providing usefull information needed by package maintainer to fix a bug is often time-consuming and sometimes out of the skill range of an ordinary Fedora user. This tool should fill this gap and help users to fill a report with all required information in just a few mouse clicks.


[edit] Comments and Discussion