Bug 679236

Summary: [abrt] glibc-2.13-1: Process /lib/ld-2.13.so was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jacques Rodary <jrodary>
Component: glibcAssignee: Andreas Schwab <schwab>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: fweimer, jakub, schwab
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:8bf931c6e3804fe827962483abc8268d4a92a8be
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-25 15:28:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Jacques Rodary 2011-02-22 01:10:11 UTC 
abrt version: 1.1.14
architecture: i686
cmdline: /lib/ld-linux.so.2 /usr/lib/libbrasero-burn.so.1.2.0
comment: rpmdb is corrupted and "rpm --rebuilddb" doesn't work. 
component: glibc
executable: /lib/ld-2.13.so
kernel: 2.6.35.11-83.fc14.i686.PAE
package: glibc-2.13-1
reason: Process /lib/ld-2.13.so was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: J'excutait la commande "rpm -Va | less". Mais le mme incident s'est dja produit avec emacs et d'autres commandes.
time: 1298318583
uid: 500

backtrace
-----
warning: core file may not match specified executable file.
[New Thread 16498]
[Thread debugging using libthread_db enabled]
../../gdb/linux-thread-db.c:1048: internal-error: attach_thread: Assertion `ti_p->ti_tid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
../../gdb/linux-thread-db.c:1048: internal-error: attach_thread: Assertion `ti_p->ti_tid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
Comment 1 Jacques Rodary 2011-02-22 01:10:14 UTC 
Created attachment 480028 [details]
File: backtrace
Comment 2 Andreas Schwab 2011-02-25 15:28:45 UTC 
Your system is broken.  Try reinstalling it.