Differences between revisions 2 and 3
Revision 2 as of 2015-02-20 11:17:17
Size: 1547
Editor: rrs
Revision 3 as of 2015-02-24 16:21:02
Size: 1616
Editor: PaulWise
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
 * '''Related projects:''' [[https://launchpad.net/apport/|apport]]

Apport for Debian

Description of the project: Apport intercepts Program crashes, collects debugging information about the crash and the operating system environment, and sends it to bug trackers in a standardized form. It also offers the user to report a bug about a package, with again collecting as much information about it as possible.

In Debian, we'd like to see Apport play flexible roles. Apport could serve as a crash detection tool, and also upon opt-in, as a Bug/Crash reporting tool. I'd also like to see functionality to save bug reports. This would allow users to save the state and then work on it later, at their leisure.

Offline Functionality: Apport has impressive retracing mechanism, where in it can download all the debug symbols for a package, to generate a proper stack trace. What to do when the crash is triggered on a box with no network? Share some ideas from apt-offline on how to download dependent packages on a different box.

  • Confirmed Mentor: Ritesh Raj Sarraf

  • How to contact the mentor: rrs@debian.org, IRC: rrs|?RickXy

  • Confirmed co-mentors: N/A

  • Deliverables of the project: Reliable detection of crashes. Integration with Debian BTS. Integration with reportbug. Offline functionality.

  • Desirable skills: Shell, Python, C, Debugging.

  • What the student will learn: Student will gain deeper knowledge of when and why programs crash (Actual bugs vs Integration Issues, Library Transitions), How to reliably detect and Debug them.

  • Related projects: apport