diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2013-06-03 17:06:55 +0200 |
---|---|---|
committer | Anthony Liguori <aliguori@us.ibm.com> | 2013-06-10 11:36:11 -0500 |
commit | bc7d0e66741724216cc104034838eb34f0e94b8d (patch) | |
tree | 1ad0ee050494fd723b0a7eb3ef7cdead02f1d07f /gdbstub.c | |
parent | 26ac7a31fbf5522d2ca3f0e2e5b5c8e915701f66 (diff) | |
download | qemu-bc7d0e66741724216cc104034838eb34f0e94b8d.tar.gz qemu-bc7d0e66741724216cc104034838eb34f0e94b8d.tar.bz2 qemu-bc7d0e66741724216cc104034838eb34f0e94b8d.zip |
gdbstub: let the debugger resume from guest panicked state
While in general we forbid a "continue" from the guest panicked
state, it makes sense to have an exception for that when continuing
in the debugger. Perhaps the guest entered that state due to a bug,
for example, and we want to continue no matter what.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Luiz Capitulino <lcapitulino@redhat.com>
Message-id: 1370272015-9659-3-git-send-email-pbonzini@redhat.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'gdbstub.c')
-rw-r--r-- | gdbstub.c | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -371,6 +371,9 @@ static inline void gdb_continue(GDBState *s) #ifdef CONFIG_USER_ONLY s->running_state = 1; #else + if (runstate_check(RUN_STATE_GUEST_PANICKED)) { + runstate_set(RUN_STATE_DEBUG); + } if (!runstate_needs_reset()) { vm_start(); } |