From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: RFA: Document conventions for terminating query/set packet names
Date: Thu, 04 May 2006 12:38:00 -0000 [thread overview]
Message-ID: <20060504123755.GA29302@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0605032313s69362babjcda4e60fe33f9d6e@mail.gmail.com>
On Wed, May 03, 2006 at 11:13:47PM -0700, Jim Blandy wrote:
> 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.
Well, I don't know it, but I strongly suspect it. I know we've gotten
boards from vendors with RedBoot flashed into them; and the life of
flashed boot monitors can be depressingly long.
Here's the deal with qPart as I see it: there is currently exactly one
OBJECT value defined, "auxv". This only applies to hosted programs
running within an OS with an ELF interpreter, and in practice I think
it only applies to GNU/Linux and Solaris. These are cases where the
stub is fairly easy to upgrade.
Now, once I get the qPart:features support merged, it'll be a different
story; that's primarily targeted at embedded stubs. But it hasn't
happened yet and I only know of a handful of users, none of whom are
committed to the interface.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-04 12:38 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
2006-05-04 12:38 ` Daniel Jacobowitz [this message]
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=20060504123755.GA29302@nevyn.them.org \
--to=drow@false.org \
--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