aboutsummaryrefslogtreecommitdiff
path: root/vl.c
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2013-06-03 17:06:55 +0200
committerAnthony Liguori <aliguori@us.ibm.com>2013-06-10 11:36:11 -0500
commitbc7d0e66741724216cc104034838eb34f0e94b8d (patch)
tree1ad0ee050494fd723b0a7eb3ef7cdead02f1d07f /vl.c
parent26ac7a31fbf5522d2ca3f0e2e5b5c8e915701f66 (diff)
downloadqemu-bc7d0e66741724216cc104034838eb34f0e94b8d.zip
qemu-bc7d0e66741724216cc104034838eb34f0e94b8d.tar.gz
qemu-bc7d0e66741724216cc104034838eb34f0e94b8d.tar.bz2
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 'vl.c')
-rw-r--r--vl.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/vl.c b/vl.c
index 47ab45d..180fdde 100644
--- a/vl.c
+++ b/vl.c
@@ -610,6 +610,7 @@ static const RunStateTransition runstate_transitions_def[] = {
{ RUN_STATE_GUEST_PANICKED, RUN_STATE_PAUSED },
{ RUN_STATE_GUEST_PANICKED, RUN_STATE_FINISH_MIGRATE },
+ { RUN_STATE_GUEST_PANICKED, RUN_STATE_DEBUG },
{ RUN_STATE_MAX, RUN_STATE_MAX },
};