Red Hat Bugzilla – Bug 849588
[abrt] gdb-188.8.131.5220801-17.fc18: gdb_bfd_unref: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 09:25:29 EST
Description of problem:
Version-Release number of selected component:
libreport version: 2.0.12
cmdline: gdb -q -nw -i mi -tty /dev/pts/2 --cd=/data/projects/gcr --command=.gdbinit /data/projects/gcr/gcr/tests/.libs/test-system-prompt
:Thread no. 1 (10 frames)
: #0 gdb_bfd_unref at ../../gdb/gdb_bfd.c
: #1 exec_close at ../../gdb/exec.c
: #2 exec_close_1 at ../../gdb/exec.c
: #3 target_close at ../../gdb/target.c
: #4 pop_all_targets_above at ../../gdb/target.c
: #5 quit_target at ../../gdb/top.c
: #6 catch_errors at ../../gdb/exceptions.c
: #7 quit_force at ../../gdb/top.c
: #9 _bfd_dwarf2_cleanup_debug_info at ../../bfd/dwarf2.c
: #10 _bfd_elf_close_and_cleanup at ../../bfd/elf.c
Created attachment 605626 [details]
Created attachment 605627 [details]
Created attachment 605629 [details]
Created attachment 605630 [details]
Created attachment 605631 [details]
Created attachment 605632 [details]
Created attachment 605633 [details]
Created attachment 605634 [details]
Created attachment 605635 [details]
From frames #7 and #8 I see that SIGTERM was delivered to gdb.
Then gdb crashed trying to process it.
I think the gdb SIGTERM handling is just broken.
In the signal handler it tries to parse and evaluate an expression,
kill inferiors, pop the target, and other things besides.
It is hard to imagine that all this is safe to do at any
arbitrary point inside gdb.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.