| Line 31: | Line 31: | ||
== How To Test == | == How To Test == | ||
Not possible yet. | Not possible yet. | ||
This section needs to be completed for FESCo submission [[User:Poelstra|poelcat]] 16:45, 4 November 2010 (UTC) | |||
== Dependencies == | == Dependencies == | ||
Revision as of 16:45, 4 November 2010
Retrace Server
Summary
Server that simplifies coredump analysis.
Owner
- Name: Michal Toman
- Email: mtoman@redhat.com
Current Status
- Targeted release: Fedora 15
- Last updated: 2010-11-03
- Percentage of completion: 40%
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.
This section needs to be completed for FESCo submission poelcat 16:45, 4 November 2010 (UTC)
Dependencies
- gdb
- xz
- mod_wsgi
- python-webob
Contingency Plan
Not required, feature can easily be disabled.