Bug 610045 - [abrt] crash in elfutils-0.147-1.fc12: elf_machine_rel_relative: Process /usr/bin/eu-unstrip was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in elfutils-0.147-1.fc12: elf_machine_rel_relative: Process /usr...
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: elfutils (Show other bugs)
(Show other bugs)
Version: 12
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Roland McGrath
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b8f9b81e884a52f64fc9eef70ef...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-01 13:09 UTC by Jayrome
Modified: 2010-07-02 18:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-02 18:43:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (121.89 KB, text/plain)
2010-07-01 13:09 UTC, Jayrome 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Jayrome 2010-07-01 13:09:47 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: eu-unstrip --core=/var/cache/abrt/ccpp-1277545484-12221/coredump -n
component: elfutils
crash_function: elf_machine_rel_relative
executable: /usr/bin/eu-unstrip
global_uuid: b8f9b81e884a52f64fc9eef70efe511a9b669362
kernel: 2.6.32.14-127.fc12.i686
package: elfutils-0.147-1.fc12
rating: 4
reason: Process /usr/bin/eu-unstrip was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Jayrome 2010-07-01 13:09:52 UTC 
Created attachment 428402 [details]
File: backtrace
Comment 2 Roland McGrath 2010-07-01 18:42:58 UTC 
That crash looks like a memory corruption or something similar, before startup of the program.  If you still have the file /var/cache/abrt/ccpp-1277545484-12221/coredump on hand, please try to repeat the cmdline above by hand and see if it reproduces the crash.  If it does not, we'll have to close this bug.
Comment 3 Jayrome 2010-07-02 03:44:22 UTC 
I checked, there's none. Sorry for the alarm.
Note You need to log in before you can comment on or make changes to this bug.