[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-trivial] [PULL 10/10] gdbstub: Set current CPU on interruptions

From: Michael Tokarev
Subject: [Qemu-trivial] [PULL 10/10] gdbstub: Set current CPU on interruptions
Date: Mon, 27 Jul 2015 22:54:13 +0300

From: Jan Kiszka <address@hidden>

gdb expects that the thread ID for c and g-class operations is set to
the CPU we provide when reporting VM stop conditions. If the stub is
still tuned to a different CPU, the wrong information is delivered to
the gdb frontend.

Signed-off-by: Jan Kiszka <address@hidden>
Signed-off-by: Michael Tokarev <address@hidden>
 gdbstub.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gdbstub.c b/gdbstub.c
index 92b2f81..ffe7e6e 100644
--- a/gdbstub.c
+++ b/gdbstub.c
@@ -1285,6 +1285,7 @@ static void gdb_vm_state_change(void *opaque, int 
running, RunState state)
         ret = GDB_SIGNAL_UNKNOWN;
+    gdb_set_stop_cpu(cpu);
     snprintf(buf, sizeof(buf), "T%02xthread:%02x;", ret, cpu_index(cpu));

reply via email to

[Prev in Thread] Current Thread [Next in Thread]