Bug 679251

Summary: [abrt] rpm-4.8.1-5.fc14: Process /bin/rpm was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jacques Rodary <jrodary>
Component: rpmAssignee: Panu Matilainen <pmatilai>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ffesti, jnovy, pmatilai
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:cd0283d8d7eb925e9a0359a6b791b5ef177b1fc1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:06:10 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 03:29:17 UTC 
abrt version: 1.1.14
architecture: i686
cmdline: rpm -V w3m
comment: no idea again
component: rpm
executable: /bin/rpm
kernel: 2.6.35.11-83.fc14.i686.PAE
package: rpm-4.8.1-5.fc14
reason: Process /bin/rpm was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: yet another crash, this time with rpm (see my other bugs reports 679240 and 679236). 
time: 1298344005
uid: 500

backtrace
-----
[New Thread 5395]
[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 03:29:19 UTC 
Created attachment 480044 [details]
File: backtrace
Comment 2 Panu Matilainen 2011-02-22 06:01:03 UTC 
When arbitrary processes start suddenly crashing all over the place, it typically means hardware failure (memory, overheating due to fan failure etc) but kernel memory corruption isn't unheard of either. The system is so ill that it fails to run the debugger.

Reboot (to clear possible memory corruption), and if the symtoms persist, take the box to a doctor.
Comment 3 Fedora End Of Life 2012-08-16 15:06:13 UTC 
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping