Commit bc7d0e66 authored by Paolo Bonzini's avatar Paolo Bonzini Committed by Anthony Liguori
Browse files

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: default avatarPaolo Bonzini <pbonzini@redhat.com>
Reviewed-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
Message-id: 1370272015-9659-3-git-send-email-pbonzini@redhat.com
Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
parent 26ac7a31

gdbstub.c

+3 −0
Original line number Diff line number Diff line
@@ -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();

    }

vl.c

+1 −0
Original line number Diff line number Diff line
@@ -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 },

};