Bug 613630 - [abrt] crash in glibc-2.11.2-1: strcmp: Process /lib64/ld-2.11.2.so was killed by signal 11 (SIGSEGV)
[abrt] crash in glibc-2.11.2-1: strcmp: Process /lib64/ld-2.11.2.so was kille...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: prelink (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Fedora Extras Quality Assurance
abrt_hash:ba6b9cf71ce6733222c7745a55f...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-12 09:10 EDT by colinmw
Modified: 2010-07-14 13:16 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-14 13:16:15 EDT
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 (7.77 KB, text/plain)
2010-07-12 09:10 EDT, colinmw
no flags Details

  None (edit)
Description colinmw 2010-07-12 09:10:26 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /lib64/ld-linux-x86-64.so.2 /usr/bin/gnomine.#prelink#.RVANfw
component: glibc
crash_function: strcmp
executable: /lib64/ld-2.11.2.so
global_uuid: ba6b9cf71ce6733222c7745a55f01e661e52737b
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-12 09:10:29 EDT
Created attachment 431170 [details]
File: backtrace
Comment 2 d. johnson 2010-07-14 13:16:15 EDT
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.