Bug 679236 - [abrt] glibc-2.13-1: Process /lib/ld-2.13.so was killed by signal 11 (SIGSEGV)
Summary: [abrt] glibc-2.13-1: Process /lib/ld-2.13.so was killed by signal 11 (SIGSEGV)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8bf931c6e3804fe827962483abc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-22 01:10 UTC by Jacques Rodary
Modified: 2016-11-24 15:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-25 15:28:45 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (651 bytes, text/plain)
2011-02-22 01:10 UTC, Jacques Rodary
no flags Details

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.


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