| commit | 00e94dbc7fd0110b0555d59592b004333adfb4b8 | |
| author | Jan Kiszka <jan.kiszka@siemens.com> | |
| Tue, 6 Mar 2012 17:32:35 +0000 (6 18:32 +0100) | ||
| committer | Blue Swirl <blauwirbel@gmail.com> | |
| Sun, 11 Mar 2012 11:23:19 +0000 (11 11:23 +0000) | ||
| tree | 9bb875252621dadf348856251a2ee2cbf3d872db | treesnapshot (tar.gz zip) |
| parent | 3f2cbf0d1a1340bed4a63e05b044c46df93f4768 | commitdiff |
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>
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>
| gdbstub.c | diffblobblamehistory |