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 <jan.kiszka@siemens.com> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
This commit is contained in:
parent
801db5ecda
commit
226d007dbd
@ -1285,6 +1285,7 @@ static void gdb_vm_state_change(void *opaque, int running, RunState state)
|
|||||||
ret = GDB_SIGNAL_UNKNOWN;
|
ret = GDB_SIGNAL_UNKNOWN;
|
||||||
break;
|
break;
|
||||||
}
|
}
|
||||||
|
gdb_set_stop_cpu(cpu);
|
||||||
snprintf(buf, sizeof(buf), "T%02xthread:%02x;", ret, cpu_index(cpu));
|
snprintf(buf, sizeof(buf), "T%02xthread:%02x;", ret, cpu_index(cpu));
|
||||||
|
|
||||||
send_packet:
|
send_packet:
|
||||||
|
Loading…
Reference in New Issue
Block a user