Bug 1117192

Summary: [abrt] gdb: memset(): gdb killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Galik <oasookee>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: gbenson, jan.kratochvil, palves, patrickm, pmuldoon, sergiodj
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0030f6e2eb2e36f38ed52eb23a426fe88ed31e1b
Whiteboard: abrt_hash:fd76ec40d0c483d71c7e585fa5d16a203a61b11f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 21:31:07 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
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 Galik 2014-07-08 09:02:14 UTC 
Description of problem:
I was using the debugger through the eclipse IDE Version: Luna Release (4.4.0) Build id: 20140612-0600

Eclipse C/C++ Development Tools Version: 8.4.0.201406111759

I had not modified any variable just stepped through the code.

Version-Release number of selected component:
gdb-7.7.1-15.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        gdb --interpreter mi2 --nx
crash_function: memset
executable:     /usr/bin/gdb
kernel:         3.14.8-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 memset at ../sysdeps/x86_64/memset.S:68
 #2 bfd_zalloc at ../../bfd/opncls.c:1011
 #3 get_section_descriptor at ../../gdb/gdb_bfd.c:351
 #4 gdb_bfd_map_section at ../../gdb/gdb_bfd.c:372
 #5 dwarf2_read_section at ../../gdb/dwarf2read.c:2245
 #6 read_indirect_string_from_dwz at ../../gdb/dwarf2read.c:16390
 #7 read_attribute_value at ../../gdb/dwarf2read.c:15969
 #8 read_attribute at ../../gdb/dwarf2read.c:16112
 #9 read_full_die_1 at ../../gdb/dwarf2read.c:14897
 #10 read_full_die at ../../gdb/dwarf2read.c:14917
Comment 1 Galik 2014-07-08 09:02:18 UTC 
Created attachment 916298 [details]
File: backtrace
Comment 2 Galik 2014-07-08 09:02:19 UTC 
Created attachment 916299 [details]
File: cgroup
Comment 3 Galik 2014-07-08 09:02:20 UTC 
Created attachment 916300 [details]
File: core_backtrace
Comment 4 Galik 2014-07-08 09:02:22 UTC 
Created attachment 916301 [details]
File: dso_list
Comment 5 Galik 2014-07-08 09:02:23 UTC 
Created attachment 916302 [details]
File: environ
Comment 6 Galik 2014-07-08 09:02:24 UTC 
Created attachment 916303 [details]
File: exploitable
Comment 7 Galik 2014-07-08 09:02:25 UTC 
Created attachment 916304 [details]
File: limits
Comment 8 Galik 2014-07-08 09:02:27 UTC 
Created attachment 916305 [details]
File: maps
Comment 9 Galik 2014-07-08 09:02:28 UTC 
Created attachment 916306 [details]
File: open_fds
Comment 10 Galik 2014-07-08 09:02:29 UTC 
Created attachment 916307 [details]
File: proc_pid_status
Comment 11 Galik 2014-07-08 09:02:30 UTC 
Created attachment 916308 [details]
File: var_log_messages
Comment 12 Jan Kratochvil 2014-07-08 11:25:28 UTC 
Could you send also the core file for this GDB crash?
So that one can debug the secondary crash:
  Assertion `!val1->optimized_out' failed.
The primary crash is not clear to me bug the core file may also help.
Comment 13 Jan Kratochvil 2014-07-09 11:05:10 UTC 
The secondary crash (=GDB crash during backtracing crashed GDB) is now fixed in:
  gdb-7.7.1-16.fc20
Comment 14 Galik 2014-07-13 15:57:55 UTC 
Sorry I don't have the core file for this.
Comment 15 Fedora End Of Life 2015-05-29 12:19:23 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.
Comment 16 Fedora End Of Life 2015-06-29 21:31:07 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.