CPU
picked is arbitrarily from the ones to be resumed, but it should be okay, as all
GDB cares about is that it is a resumed thread.
Signed-off-by: Matheus Branco Borella
---
gdbstub/gdbstub.c | 29 ++
tests/tcg/multiarch/gdbstub/interrupt.py | 99 ++
CPU
picked is arbitrarily from the ones to be resumed, but it should be okay, as all
GDB cares about is that it is a resumed thread.
Signed-off-by: Matheus Branco Borella
---
gdbstub/gdbstub.c | 29 ++
tests/tcg/multiarch/gdbstub/interrupt.py | 99 ++
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1725
This fix is implemented by having the vCont handler set the value of
`gdbserver_state.c_cpu` if any threads are to be resumed. The specific CPU
is picked arbitrarily from the ones to be resumed, but it should be okay, as all
GDB cares ab
