Red Hat Bugzilla – Bug 991597
[abrt] gdb-7.6-32.fc19: dump_core: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Last modified: 2015-02-17 11:31:54 EST
Version-Release number of selected component:
cmdline: gdb -batch -ex 'set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug' -ex 'file /usr/bin/dfa_determinize' -ex 'core-file ./coredump' -ex 'thread apply all backtrace 1024 full' -ex 'info sharedlib' -ex 'print (char*)__abort_msg' -ex 'print (char*)__glib_assert_msg' -ex 'info registers' -ex disassemble
runlevel: N 5
Thread no. 1 (10 frames)
#2 dump_core at ../../gdb/utils.c:761
#3 internal_vproblem at ../../gdb/utils.c:919
#4 internal_verror at ../../gdb/utils.c:944
#5 internal_error at ../../gdb/utils.c:954
#6 regcache_raw_supply at ../../gdb/regcache.c:997
#7 i386_supply_gregset at ../../gdb/i386-tdep.c:3209
#8 get_core_register_section at ../../gdb/corelow.c:614
#9 get_core_registers at ../../gdb/corelow.c:652
#10 target_fetch_registers at ../../gdb/target.c:4017
#11 regcache_raw_read at ../../gdb/regcache.c:612
Potential duplicate: bug 716627
Created attachment 782169 [details]
Created attachment 782170 [details]
Created attachment 782171 [details]
Created attachment 782172 [details]
Created attachment 782173 [details]
Created attachment 782174 [details]
Created attachment 782175 [details]
Created attachment 782176 [details]
Created attachment 782177 [details]
Created attachment 782178 [details]
I compile the cactus jukebox 0.4.2stable with lazarus ide. Compilation was successful and i pressed F9 button to run player and retrive the next message of lazarus:
Ooops, the debugger entered the error state
Save your work now !
Hit Stop, and hope the best? we're pulling the plug.
The GDB process is no longer running
The GDB command:
"info functions FPC_CPUINIT"
did not return any result.
The GDB process is no longer running.
cmdline: /usr/bin/gdb -silent -i mi -nx
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
runlevel: N 5
Another user experienced a similar problem:
in KDevelop, debugged and stepped into a statement (iirc it was "mpOutputDevice->SetClipRegion(Region(maClipPolyPolygon));" which is unique in LibreOffice)
cmdline: gdb --interpreter=mi2 -quiet
reason: gdb killed by SIGABRT
runlevel: N 5
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.