Bug 646270

Summary: [abrt] gdb-7.1-34.fc13: htab_hash_string: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Leandro Costa Silva <leandro>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: jan.kratochvil, pmuldoon, tromey
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1e8f5019ab59cc47e17c167dc93d39305e993e9b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-19 12:57:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Leandro Costa Silva 2010-10-25 02:17:40 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gdb -batch -ex 'set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug' -ex 'file /usr/lib64/firefox-3.6/firefox' -ex 'core-file /var/spool/abrt/ccpp-1287972384-2610/coredump' -ex 'thread apply all backtrace 2048 full' -ex 'info sharedlib' -ex 'print (char*)__abort_msg' -ex 'print (char*)__glib_assert_msg' -ex 'info registers' -ex disassemble
component: gdb
crash_function: htab_hash_string
executable: /usr/bin/gdb
kernel: 2.6.34.7-61.fc13.x86_64
package: gdb-7.1-34.fc13
rating: 4
reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1287972400
uid: 500
Comment 1 Leandro Costa Silva 2010-10-25 02:17:43 UTC 
Created attachment 455384 [details]
File: backtrace
Comment 2 Fedora Admin XMLRPC Client 2011-01-06 03:24:37 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Bug Zapper 2011-05-31 10:43:16 UTC 
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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
Comment 4 Jan Kratochvil 2011-05-31 18:44:33 UTC 
Unaware whether it is already fixed or a still valid bug.
Comment 5 Tom Tromey 2012-09-13 16:30:28 UTC 
It's hard to see how this failure could happen with
the current gdb.  It would require a NULL 'mangled'
entry in the demangled name hash; but that seems like
a "can't happen".

Also note that this is the same .so as in bug #645733.
Both bugs could be caused by the same symptom, though
the trace in #645733 is not complete enough to say for sure.
Comment 6 Jan Kratochvil 2012-12-19 12:57:43 UTC 
I have checked gdb-7.1-34.fc13 and I do not see how that could happen there.