Features/RetraceServer

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Dependencies)
(Current Status)
Line 12: Line 12:
 
== Current Status ==
 
== Current Status ==
 
* Targeted release: [[Releases/15 | Fedora 15]]
 
* Targeted release: [[Releases/15 | Fedora 15]]
* Last updated: 2010-10-04
+
* Last updated: 2010-10-12
 
* Percentage of completion: 10%
 
* Percentage of completion: 10%
  

Revision as of 16:33, 12 October 2010

Contents

Retrace Server

Summary

Server that simplifies coredump analysis.

Owner

  • Email: mtoman@redhat.com

Current Status

  • Targeted release: Fedora 15
  • Last updated: 2010-10-12
  • Percentage of completion: 10%

Detailed description

At the moment of backtrace creation, user needs to have all relevant debuginfos installed locally. Downloading and installing them may require a lot of time and storage space. The idea of Retrace Server is to liberate users from this: User sends the coredump packed along with some other required information (e.g. packages list) to the Retrace Server, the Retrace Server installs required debuginfos, creates backtrace and provides it to the user.

Benefit to Fedora

No need to download debuginfo packages while creating backtrace from various binary crashes.

Scope

The project itself consists of 3 parts:

  • Interface: Receives the archive from user, unpacks all files, puts new task into the queue.
  • Analyzer: Takes the task from queue, for each creates a virtual root with all required packages and debuginfos installed and creates the backtrace within.
  • Repo Synchronizer: Downloads packages to a local repository containing all versions of all packages, to be able to handle crashes from older versions.

ABRT plugin that packs required files and sends the archive to the Retrace Server must be implemented.

How To Test

Not possible yet.

Dependencies

  • gdb
  • xz
  • mod_wsgi

Contingency Plan

Not required, feature can easily be disabled.

Documentation

Comments and Discussion