The sequence of gdb commands here is a bit odd since it's switching the
gdb session from targeting a remote gdb stub to targeting a local
executable. However, if you want to do this without killing QEMU you
can:
(gdb) target remote :1234
(gdb) detach
(gdb) target exec /bin/ls
The 'detach' tells gdb to disconnect from the remote gdbstub without
killing the QEMU session.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1603580
Title:
[gdbstub] qemu is killed when using remote debugger with qemu -S -s
Status in QEMU:
Invalid
Bug description:
Hello,
REPRODUCE
$ qemu-system-x86_64 -s -S -nographic
<wait>
QEMU: Terminated via GDBStub
$ gdb
(gdb) target remote :1234
(gdb) load /bin/ls
(gdb) target exec
A program is being debugged already. Kill it? (y or no) y
No executable file now.
EXPECTED
Enable program to be executed without terminating QEMU.
DISCUSSION
This was already discussed in [1], reverted in [2], however, no
solution is provided.
It worked perfectly in the past, I guess because of [1] and before
[3].
Opening bug for this as discussion in mailing list did not attract
anyone and functionality is required. If there is other gdb sequence
to achieve same result it would be great to get it documented.
Thanks,
[1]
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=00e94dbc7fd0110b0555d59592b004333adfb4b8
[2]
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=ce0274f730eacbd24c706523ddbbabb6b95d0659
[3]
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7d03f82f81e0e6c106ca0d2445a0fc49dc9ddc7b
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1603580/+subscriptions
