On 10/26/2016 08:56 AM, Christian Borntraeger wrote: > On 10/14/2016 01:53 PM, Claudio Imbrenda wrote: >> When GDB issues a "vCont", QEMU was not handling it correctly when >> multiple VCPUs are active. >> For vCont, for each thread (VCPU), it can be specified whether to >> single step, continue or stop that thread. The default is to stop a >> thread.
Or more accurately, to leave it stopped as it was. >> However, when (for example) "vCont;s:2" is issued, all VCPUs continue >> to run, although all but VCPU nr 2 are to be stopped. > > Any gdbstub expert in the house? I'm not a qemu gdbstub expert, but FYI, seeing this reminded me to push to gdb's master a (getting old) gdb patch that clarifies how vCont actions should be interpreted: https://sourceware.org/ml/gdb-patches/2016-02/msg00493.html It's already live at: https://sourceware.org/gdb/current/onlinedocs/gdb/Packets.html (The "already running" case is for non-stop mode, which qemu probably doesn't support.) Thanks, Pedro Alves
