summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorJan Kiszka2012-03-06 18:32:35 +0100
committerBlue Swirl2012-03-11 12:23:19 +0100
commit00e94dbc7fd0110b0555d59592b004333adfb4b8 (patch)
tree9bb875252621dadf348856251a2ee2cbf3d872db /Makefile
parenttarget-i386: Mask NX bit from cpu_get_phys_page_debug result (diff)
downloadqemu-00e94dbc7fd0110b0555d59592b004333adfb4b8.tar.gz
qemu-00e94dbc7fd0110b0555d59592b004333adfb4b8.tar.xz
qemu-00e94dbc7fd0110b0555d59592b004333adfb4b8.zip
gdbstub: Do not kill target in system emulation mode
Too many VM kittens were killed since 7d03f82f81. Another one just died under my fat fingers. When you quit a kgdb session, does the Linux kernel power off? Or when you terminate gdb attached to a hardware debugger, does your board vanish in space? No. So let's stop terminating QEMU when the gdbstub receives a kill commando in system emulation mode. Real termination can still be achieved via "monitor quit". We keep the behavior for user mode emulation which is arguably more like a gdbserver scenario. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions