[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 2/2] gdbstub: Fix vCont behaviour
From: |
Claudio Imbrenda |
Subject: |
Re: [Qemu-devel] [PATCH v2 2/2] gdbstub: Fix vCont behaviour |
Date: |
Fri, 28 Oct 2016 15:35:20 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 |
On 27/10/16 13:40, Pedro Alves wrote:
> 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.)
>From the new specifications I seem to understand that if I specify a
default as first action, then no further actions will be considered,
since it matches all threads?
e.g. vCont;c;s:1 will ignore the s:1 because the c was specified
earlier and it matches all threads, and therefore it's the leftmost
match? do I understand correctly?
Or does the default only match any thread without an explicit match?
(which is how I interpreted the old spec)
[Qemu-devel] [PATCH v2 1/2] move vm_start to cpus.c, Claudio Imbrenda, 2016/10/14