From 226d007dbd75ec8d0f12d0f9e1ce66caf55d49e4 Mon Sep 17 00:00:00 2001 From: Jan Kiszka Date: Fri, 24 Jul 2015 18:52:31 +0200 Subject: [PATCH] gdbstub: Set current CPU on interruptions 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 Signed-off-by: Michael Tokarev --- gdbstub.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gdbstub.c b/gdbstub.c index 92b2f81584..ffe7e6efb2 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; break; } + gdb_set_stop_cpu(cpu); snprintf(buf, sizeof(buf), "T%02xthread:%02x;", ret, cpu_index(cpu)); send_packet: -- 2.11.0