Bug 613346 - [abrt] crash in glibc-2.11.2-1: elf_machine_rela_relative: Process /lib64/ld-2.11.2.so was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in glibc-2.11.2-1: elf_machine_rela_relative: Process /lib64/ld-...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0913dbb0cf9f70c71d9a4db0db8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-10 23:12 UTC by colinmw
Modified: 2017-10-09 13:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-11 06:03:05 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (3.38 KB, text/plain)
2010-07-10 23:12 UTC, colinmw 		no flags Details
View All

Description colinmw 2010-07-10 23:12:37 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /lib64/ld-linux-x86-64.so.2 /usr/lib64/libgcj-tools.so.10.0.0.#prelink#.lZEyon
component: glibc
crash_function: elf_machine_rela_relative
executable: /lib64/ld-2.11.2.so
global_uuid: 0913dbb0cf9f70c71d9a4db0db862de30b51c355
kernel: 2.6.32.14-127.fc12.x86_64
package: glibc-2.11.2-1
rating: 4
reason: Process /lib64/ld-2.11.2.so was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 colinmw 2010-07-10 23:12:40 UTC 
Created attachment 430924 [details]
File: backtrace
Comment 2 d. johnson 2010-07-11 06:03:05 UTC 
Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are no debugging symbols loaded (probably abrt failed to load them).

Unfortunately, we cannot use this backtrace.

Closing as INSUFFICIENT_DATA.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Note You need to log in before you can comment on or make changes to this bug.