Bug 588129 - [abrt] crash in abrt-1.0.9-1.fc12: Process /usr/bin/abrt-backtrace was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in abrt-1.0.9-1.fc12: Process /usr/bin/abrt-backtrace was killed...
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Karel Klíč
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:cdef74d18965ad7c08845820ded...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-02 19:34 UTC by Bryan Dawson
Modified: 2013-03-03 23:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-10-25 10:29:08 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (9.00 KB, text/plain)
2010-05-02 19:34 UTC, Bryan Dawson
no flags Details

Description Bryan Dawson 2010-05-02 19:34:40 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: abrt-backtrace --single-thread --remove-exit-handlers --frame-depth=5 --remove-noncrash-frames /var/cache/abrt/ccpp-1272692114-23458/backtrace
component: abrt
executable: /usr/bin/abrt-backtrace
global_uuid: cdef74d18965ad7c08845820dedceb27e00300f3
package: abrt-1.0.9-1.fc12
rating: 4
reason: Process /usr/bin/abrt-backtrace was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. Happens trying to update through Gnome (System -> Administration -> Software Update

Comment 1 Bryan Dawson 2010-05-02 19:34:42 UTC
Created attachment 410845 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-06 11:08:14 UTC
Hi Bryan,

can you, please, also attach the backtrace which caused the crash? It would help a lot. It should be in /var/cache/abrt/ccpp-1272692114-23458/backtrace

Comment 3 Karel Klíč 2010-10-25 10:29:08 UTC
This bug is fixed in upstream git repository, which will become abrt-1.1.14 at some point. As the fix was very intrusive (changing a lot of code), and it is dangerous to update Fedora 12/13 with it (no decision about F-14 yet). Fedora 15 will contain the fix for sure.

Note You need to log in before you can comment on or make changes to this bug.