gdbstub: fix for commit 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc

This commit used the wrong check to prevent an assertion failure.
After this commit, you need to start a guest in the monitor, you
cannot use anymore the "c" command in the debugger.  This is
undesirable.  The commit's aim was to prevent a restart
after a KVM internal error or something like that; use
runstate_needs_reset() for that.

Signed-off-by: Paolo Bonzini <[email protected]>
Reviewed-by: Luiz Capitulino <[email protected]>
Message-id: 1370272015[email protected]
Signed-off-by: Anthony Liguori <[email protected]>

diff --git a/gdbstub.c b/gdbstub.c
index 90e54cb4e352b9cc5c241c2b4e4ee37e2167a9cb..e8541f365d3e450784c9ab45a7acd73fe504cef1 100644 (file)
--- a/gdbstub.c
+++ b/gdbstub.c
@@ -371,7 +371,7 @@ static inline void gdb_continue(GDBState *s)
 #ifdef CONFIG_USER_ONLY
     s->running_state = 1;
 #else
-    if (runstate_check(RUN_STATE_DEBUG)) {
+    if (!runstate_needs_reset()) {
         vm_start();
     }
 #endif