Bug 1019878

Summary: [abrt] gdb-7.6.1-42.fc19: htab_hash_string: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: antking
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gbenson, jan.kratochvil, palves, pmuldoon, sergiodj, tromey
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d7bb4f212a6404850072576e67cb47c1c37cf291
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-18 13:07:38 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description antking 2013-10-16 14:41:10 UTC 
Version-Release number of selected component:
gdb-7.6.1-42.fc19

Additional info:
reporter:       libreport-2.1.8
backtrace_rating: 4
cmdline:        gdb --batch -ex 'python execfile(\"/usr/libexec/abrt-gdb-exploitable\")' -ex 'core-file ./coredump' -ex 'abrt-exploitable 4 ./exploitable'
crash_function: htab_hash_string
executable:     /usr/bin/gdb
kernel:         3.11.4-201.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 htab_hash_string at ../../libiberty/hashtab.c:847
 #1 htab_expand at ../../libiberty/hashtab.c:574
 #2 htab_find_slot_with_hash at ../../libiberty/hashtab.c:653
 #3 htab_find_slot at ../../libiberty/hashtab.c:712
 #4 symbol_set_names at ../../gdb/symtab.c:732
 #5 prim_record_minimal_symbol_full at ../../gdb/minsyms.c:920
 #6 record_minimal_symbol at ../../gdb/elfread.c:216
 #7 elf_symtab_read at ../../gdb/elfread.c:560
 #8 elf_symfile_read at ../../gdb/elfread.c:2320
 #9 read_symbols at ../../gdb/symfile.c:827

Potential duplicate: bug 823385
Comment 1 antking 2013-10-16 14:41:15 UTC 
Created attachment 812971 [details]
File: backtrace
Comment 2 antking 2013-10-16 14:41:18 UTC 
Created attachment 812972 [details]
File: cgroup
Comment 3 antking 2013-10-16 14:41:22 UTC 
Created attachment 812973 [details]
File: core_backtrace
Comment 4 antking 2013-10-16 14:41:26 UTC 
Created attachment 812974 [details]
File: dso_list
Comment 5 antking 2013-10-16 14:41:29 UTC 
Created attachment 812975 [details]
File: environ
Comment 6 antking 2013-10-16 14:41:32 UTC 
Created attachment 812976 [details]
File: exploitable
Comment 7 antking 2013-10-16 14:41:36 UTC 
Created attachment 812978 [details]
File: limits
Comment 8 antking 2013-10-16 14:41:40 UTC 
Created attachment 812979 [details]
File: maps
Comment 9 antking 2013-10-16 14:41:44 UTC 
Created attachment 812980 [details]
File: open_fds
Comment 10 antking 2013-10-16 14:41:47 UTC 
Created attachment 812981 [details]
File: proc_pid_status
Comment 11 antking 2013-10-16 14:41:50 UTC 
Created attachment 812982 [details]
File: var_log_messages
Comment 12 antking 2013-10-18 13:07:38 UTC 
Folks, I think this turned out to be a false alarm, at least my bug report. A change of RAM seemed to have cleared all the numerous problems I was experiencing with Fedora 19 on my new system build.

Apologies for the false alarm, and thanks for all the work you debuggers put in for the rest of us.

A. King