Alex Bennée writes:
> Can gdb switch which packet sequence it uses to halt and restart
> threads?
Yes, but the way it does it does not trigger the behavior I was concerned
about. GDB falls back to the old sequence when either (1) the target does not
support the vCont command it's trying to send
Matheus Branco Borella writes:
> 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
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
