Apport

Differences between revisions 2 and 3
Revision 2 as of 2006-10-23 08:28:38
Size: 998
Editor: p54B3FFFD
Comment: skeleton
Revision 3 as of 2006-10-23 08:39:11
Size: 2414
Editor: p54B3FFFD
Comment: write intro
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Intro, spec Debugging program crashes without any automated tools has pretty time consuming and hard for both developers and users. Many program crashes remain unreported or unfixed because:

 * Many crashes are not easily reproducible.
 * End users do not know how to prepare a report that is really useful for developers, like building a package with debug symbols, operating `gdb`, etc.
 * A considerable part of bug triage is spent with collecting relevant information about the crash itself, package versions, hardware architecture, operating system version, etc.
 * There is no easy frontend which allow users to submit detailed problem reports.
 * Existing solutions like bug-buddy or krash are specific to a particular desktop environment, are nontrivial to adapt to the needs of a distribution developer, and do not work for crashes of background servers (like a database or an email server).

Apport is a system which

 * intercepts crashes right when they happen the first time,
 * gathers potentially useful information about the crash and the OS environment,
 * and presents an UI that informs about the crash and instructs the user how to proceed.

We hope that this will lead to a much better level of quality assurance in the future.
Line 30: Line 44:

== Further links ==

 * Original specifications: [https://wiki.ubuntu.com/AutomatedProblemReports apport design], [https://wiki.ubuntu.com/CrashReporting User interface]

Apport - Automatic crash reports

What is this all about?

Debugging program crashes without any automated tools has pretty time consuming and hard for both developers and users. Many program crashes remain unreported or unfixed because:

  • Many crashes are not easily reproducible.
  • End users do not know how to prepare a report that is really useful for developers, like building a package with debug symbols, operating gdb, etc.

  • A considerable part of bug triage is spent with collecting relevant information about the crash itself, package versions, hardware architecture, operating system version, etc.
  • There is no easy frontend which allow users to submit detailed problem reports.
  • Existing solutions like bug-buddy or krash are specific to a particular desktop environment, are nontrivial to adapt to the needs of a distribution developer, and do not work for crashes of background servers (like a database or an email server).

Apport is a system which

  • intercepts crashes right when they happen the first time,
  • gathers potentially useful information about the crash and the OS environment,
  • and presents an UI that informs about the crash and instructs the user how to proceed.

We hope that this will lead to a much better level of quality assurance in the future.

How does it look like for users?

workflow, screenshot

I'm a developer. How to I use these crash reports?

report format, apport-retrace

How does it work internally?

kernel patch, crashdump-helper, report, update-notifier, inotify, apport-gtk

Future plans

port to upstream kernels, separate database, automatic submission

Use the source, Luke!

Apport (last edited 2017-05-25 20:03:48 by penalvch)