Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jim Blandy" <jimb@red-bean.com>
To: gdb-patches@sourceware.org
Subject: Re: RFA: Document conventions for terminating query/set packet names
Date: Thu, 04 May 2006 06:13:00 -0000	[thread overview]
Message-ID: <8f2776cb0605032313s69362babjcda4e60fe33f9d6e@mail.gmail.com> (raw)
In-Reply-To: <20060504015712.GA19810@nevyn.them.org>

On 5/3/06, Daniel Jacobowitz <drow@false.org> wrote:
> On Wed, May 03, 2006 at 03:54:17PM -0700, Jim Blandy wrote:
> > > I think the best solution would be to document that new packets should
> > > not start with "qP" or "qL", and rename the relatively new qPart packet
> > > to something else, like qXfer.  I don't really care whether GDB
> > > continues to try the old qPart name; I think it may be recent enough
> > > that we can drop it, but maybe not.  I believe the only thing it's used
> > > for on HEAD is the ELF Auxv vector; I have other uses on various
> > > branches, but none of them have been merged yet.
> > >
> > > Interested in any comments...
> >
> > The protocol as currently documented is ambiguous.  Whatever we do in
> > the long run, I think the manual ought to make some recommendation now
> > to guide new implementations.  The 'count the hex digits' is one
> > approach; another would be to deprecate qP altogether, in favor of
> > qThreadExtraInfo.  That's what GDB prefers at the moment; it's been
> > around since 2000.  qP dates to GDB's prehistory, but I'm pretty sure
> > it's from around 1998; I was at Cygnus when it was discussed.
>
> Could you explain why you prefer either of these changes - both of
> which affect existing stubs - to my suggestion of renaming qPart and
> the proposed qPacketInfo?
>
> I might be missing something - but it seems virtually certain that
> there are deployed stubs using qP that are going to live for a long
> time - especially since RedBoot uses it and that tends to get flashed
> into things!

It's my impression that renaming qPart will also affect existing stubs
--- isn't that so?  From looking around, it seemed to me that there
weren't too many implementations of qP, so I'm presuming that, if
something is to be broken, that'd be the one to break.  But if you
know that RedBoot is more widely installed in inaccessible places,
then that's something I didn't realize.


  reply	other threads:[~2006-05-04  6:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 19:51 Jim Blandy
2006-05-03 19:56 ` Daniel Jacobowitz
2006-05-03 22:54   ` Jim Blandy
2006-05-04  1:57     ` Daniel Jacobowitz
2006-05-04  6:13       ` Jim Blandy [this message]
2006-05-04 12:38         ` Daniel Jacobowitz
2006-05-04 17:24           ` Jim Blandy
2006-05-05 10:06             ` Eli Zaretskii
2006-05-05 19:14               ` Jim Blandy
2006-05-05 19:15               ` Jim Blandy
2006-05-05 19:18               ` Jim Blandy
2006-05-05 21:49                 ` Eli Zaretskii
2006-05-05 21:59                   ` Jim Blandy
2006-05-05 22:09                     ` Eli Zaretskii
2006-05-05 16:25             ` Daniel Jacobowitz
2006-05-09 20:41               ` Daniel Jacobowitz
2006-05-09 21:16                 ` Andrew Cagney
2006-05-10  3:18                 ` Eli Zaretskii
2006-05-14 17:09                   ` Daniel Jacobowitz
2006-05-10 21:14                 ` Jim Blandy
2006-05-04 15:55 ` Eli Zaretskii

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=8f2776cb0605032313s69362babjcda4e60fe33f9d6e@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb-patches@sourceware.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