From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/RFC: vCont for the remote protocol [doco]
Date: Tue, 30 Sep 2003 15:37:00 -0000 [thread overview]
Message-ID: <3F79A31C.8050403@redhat.com> (raw)
In-Reply-To: <20030930145103.GA26117@nevyn.them.org>
> packet ->> "vCont" { field }+
>> field ->> ";" action [ ":" tid ]
>>
>> which is very easy to parse. BTW, intro has this to say, so there
>> aren't any guidelines :-(
>
>
> That loses the requirement that the default action be last, which I'd
> like to hold on to - OK?
Was that to ensure that there wasn't more than one default action? I
think its better to instead clarify that in the text part of the spec vis:
"By default all unspecified threads remain stopped. An action with no
corresponding {tdid} shall be applied to all threads with out an
explicitly specified action. A packet specifying multiple default
actions is erreneous."
Looking at the new gdbserver code it's pratically doing this now. BTW,
I think it gets confused by the incorrect "...;cccccccccc", simplifying
to be strictly LL1 will fix that.
> I dislike the ';' because vCont is not an item in the list of actions
> that the semicolons are separating; that turns ';' from a separator
> into a prefix. But hey, prefixes are people too.
Seperator or terminator?
Andrew
next prev parent reply other threads:[~2003-09-30 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 15:29 Daniel Jacobowitz
2003-09-29 21:17 ` Andrew Cagney
2003-09-29 21:25 ` Daniel Jacobowitz
2003-09-30 14:37 ` Andrew Cagney
2003-09-30 14:51 ` Daniel Jacobowitz
2003-09-30 15:37 ` Andrew Cagney [this message]
2003-09-30 21:16 ` [v2] " Daniel Jacobowitz
2003-10-01 14:32 ` Andrew Cagney
2003-10-10 2:21 ` Andrew Cagney
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=3F79A31C.8050403@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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