Bug 692802 - Missing debuginfo for fedora15/sleep crash on abrt retrace server
Summary: Missing debuginfo for fedora15/sleep crash on abrt retrace server
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 15
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Michal Toman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-01 08:35 UTC by David Kutálek
Modified: 2015-03-23 00:41 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-02 12:25:26 UTC
Type: ---

Attachments (Terms of Use)
Backtrace generated by retrace server for sleep crash (F15) (1.62 KB, text/plain)
2011-04-01 08:35 UTC, David Kutálek 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description David Kutálek 2011-04-01 08:35:56 UTC 
Created attachment 489322 [details]
Backtrace generated by retrace server for sleep crash (F15)

Description of problem:

Backtrace generated by default retrace server in Fedora15 for sleep from Fedora15 is missing some debuginfos - see attachment.

Version-Release number of selected component (if applicable):

abrt-2.0.0-3.fc15.i686
abrt-gui-2.0.0-3.fc15.i686
abrt-plugin-bugzilla-2.0.0-3.fc15.i686
coreutils-8.10-2.fc15.i686

How reproducible:

Always

Steps to Reproduce:
1. Crash sleep & ask retrace server for backtrace.
2.
3.
  
Actual results:

Something is missing in backtrace.

Expected results:

Complete and useful backtrace.
Additional info:
Comment 1 Michal Toman 2011-04-01 09:32:41 UTC 
The backtrace is complete and useful. The missing debuginfo matches to kernel debuginfo. After discussing with Jan Kratochvil, we found that this one is probably not required for generating the backtrace. Installing 1.2 GB of kernel debuginfo would be a significant slowdown especially for simple applications: sleep chroot's size is now ~500 MB (vs ~1.7 GB).
Note You need to log in before you can comment on or make changes to this bug.