From: Luc Michel <luc.michel@greensocs.com>
To: Lucien Murray-Pitts <lucienmp_antispam@yahoo.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix for RSP vCont packet
Date: Fri, 1 Feb 2019 14:33:10 +0100 [thread overview]
Message-ID: <622bb639-5ab5-d427-e84f-bc3ef85c83da@greensocs.com> (raw)
In-Reply-To: <20190131044837.9542-1-lucienmp_antispam@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2946 bytes --]
Hi Lucien,
On 1/31/19 5:48 AM, Lucien Murray-Pitts wrote:
> The result is that vCont now does not recognise the case where no process/thread is provided after the action.
>
> This may not show up with GDB, but using Lauterbach Trace32, and Hexrays IDA Pro this issue is immediately seen.
> The response is a "$#00" empty packet, showing it is unsupported packet.
>
> This is defined in the RSP document as "An action with no thread-id matches all threads."
> (https://sourceware.org/gdb/current/onlinedocs/gdb/Packets.html#vCont-packet )
>
> Thus the valid vCont packets now are as below, however parsing is still not very strict.
> vCont;c/s - Step/Continue all threads
> vCont;c/s:[pX.]Y - Step/Continue optional process X, thread Y
> vCont;C##/S##:[pX.]Y - Step/Continue with signal ## on optional process X, thread Y
> * If X or Y are -1 then it applies the action to all processes/threads.
>
> Signed-off-by: Lucien Murray-Pitts <lucienmp_antispam@yahoo.com>
> ---
> gdbstub.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/gdbstub.c b/gdbstub.c
> index bfc7afb509..ce0dde2e24 100644
> --- a/gdbstub.c
> +++ b/gdbstub.c
> @@ -1169,6 +1169,7 @@ static int is_query_packet(const char *p, const char *query, char separator)
> */
> static int gdb_handle_vcont(GDBState *s, const char *p)
> {
> + GDBThreadIdKind vcontThreadType ;
The coding style for variable names is lower_case_with_underscores (see
CODING_STYLE). I think you can go with a simpler name like
GDBThreadIdKind kind;
> int res, signal = 0;
> char cur_action;
> char *newstates;
> @@ -1218,12 +1219,23 @@ static int gdb_handle_vcont(GDBState *s, const char *p)
> goto out;
> }
>
> - if (*p++ != ':') {
> + /*
> + * In the case we have vCont;c or vCont;s - action is on all threads
> + * Alternatively vCont;c;s:p1.1 is a possible, but meaningless format,
> + * And in the else the "vCont;c:p1.1;... format is supported.
> + */> + if (*p == '\0' || *p == ';') {
> + vcontThreadType = GDB_ALL_THREAD ;> + pid = 1 ;
The spec is not clear but I would opt for GDB_ALL_PROCESSES instead of
GDB_ALL_THREAD here. pid = 1; is clearly wrong since you don't know if
this PID exists or is currently attached.
> + tid = 1 ;
This one is not useful either (not used in the switch..case bellow).
Thanks
Luc
> + } else if (*p++ == ':') {
> + vcontThreadType = read_thread_id(p, &p, &pid, &tid) ;
> + } else {
> res = -ENOTSUP;
> goto out;
> }
>
> - switch (read_thread_id(p, &p, &pid, &tid)) {
> + switch (vcontThreadType) {
> case GDB_READ_THREAD_ERR:
> res = -EINVAL;
> goto out;
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-01 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 4:48 [Qemu-devel] [PATCH] Fix for RSP vCont packet Lucien Murray-Pitts
2019-01-31 12:58 ` Eric Blake
2019-02-01 13:33 ` Luc Michel [this message]
2019-02-01 14:25 ` Lucien Anti-Spam
2019-02-05 14:54 ` Luc Michel
-- strict thread matches above, loose matches on Subject: below --
2019-03-04 7:39 Lucien Murray-Pitts
2019-03-04 10:05 ` Luc Michel
[not found] <1814910652.595504.1548895281698.ref@mail.yahoo.com>
2019-01-31 0:41 ` Lucien Anti-Spam
2019-01-31 3:47 ` Eric Blake
2019-01-31 4:10 ` Lucien Anti-Spam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=622bb639-5ab5-d427-e84f-bc3ef85c83da@greensocs.com \
--to=luc.michel@greensocs.com \
--cc=lucienmp_antispam@yahoo.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).