Description of problem: gdb crashed while I was connected to qemu's gdbstub when playing with x86 real-mode bootloader code. Interrupting x86 real-mode execution with <CTRL-C> then pressing <CTRL-D> to quit gdb seems to cause it. Version-Release number of selected component: gdb-7.6.50.20130731-19.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: gdb -q -x examine-stack.gdb crash_function: dump_core executable: /usr/bin/gdb kernel: 3.13.5-202.fc20.x86_64 runlevel: N 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (10 frames) #2 dump_core at ../../gdb/utils.c:648 #3 internal_vproblem at ../../gdb/utils.c:807 #4 internal_verror at ../../gdb/utils.c:833 #5 internal_error at ../../gdb/utils.c:843 #6 target_mourn_inferior at ../../gdb/target.c:2850 #7 kill_or_detach at ../../gdb/top.c:1316 #8 iterate_over_inferiors at ../../gdb/inferior.c:396 #9 quit_force at ../../gdb/top.c:1424 #10 execute_command at ../../gdb/top.c:482 #11 command_handler at ../../gdb/event-top.c:433 Potential duplicate: bug 716627
Created attachment 875788 [details] File: backtrace
Created attachment 875789 [details] File: cgroup
Created attachment 875790 [details] File: core_backtrace
Created attachment 875791 [details] File: dso_list
Created attachment 875792 [details] File: environ
Created attachment 875793 [details] File: limits
Created attachment 875794 [details] File: maps
Created attachment 875795 [details] File: open_fds
Created attachment 875796 [details] File: proc_pid_status
Created attachment 875797 [details] File: var_log_messages
Another user experienced a similar problem: I created a very simple Lazarus/FreePascal program to execute within the IDE to demonstrate variables as such: procedure TForm1.Button1Click(Sender: TObject); var str1 : string[10]; begin str1 := 'byte me'; edit1.Text := str1[2]; sleep(10); end; I then set a breakpoint on line 6 to stop execution to check values. Hovering over str1 showed: str1='byte me', however when I hovered over .Text gdb crashed. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/bin/gdb -silent -i mi -nx crash_function: dump_core executable: /usr/bin/gdb kernel: 3.13.10-200.fc20.x86_64 package: gdb-7.6.50.20130731-19.fc20 reason: gdb killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was running a project reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gdb -silent -i mi -nx crash_function: dump_core executable: /usr/bin/gdb kernel: 3.16.7-200.fc20.x86_64 package: gdb-7.7.1-21.fc20 reason: gdb killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: After setting a breakpoint and reaching the breakpoint, attempted to step further through program. Upon stepping GDB crashed. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gdb --interpreter mi2 --nx crash_function: dump_core executable: /usr/bin/gdb kernel: 3.18.7-100.fc20.x86_64 package: gdb-7.7.1-21.fc20 reason: gdb killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
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.
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.