From: Michael Eager <eager@eagercon.com>
To: Michael Eager <eager@eagercon.com>, Eli Zaretskii <eliz@gnu.org>,
stanshebs@earthlink.net, gdb@sources.redhat.com
Subject: Re: What's an annex? stratum?
Date: Sat, 23 Jun 2007 21:40:00 -0000 [thread overview]
Message-ID: <467D934C.10909@eagercon.com> (raw)
In-Reply-To: <20070623212355.GA3448@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Sat, Jun 23, 2007 at 01:51:50PM -0700, Michael Eager wrote:
>> The doc refers to a non-existent DTD file which is supposed to
>> describe the XML target description annex. I assumed it was obsolete.
>
> You are looking at mismatched source and manual, I assume - you didn't
> say what versions you were using. In the HEAD version and snapshots,
> gdb/features/gdb-target.dtd does exist and the documentation describes
> it. The most accessible copy of the online docs refers to HEAD; I
> wonder if we should make the manual for the last release more
> prominent instead.
I'm looking at the current CVS tree. Perhaps my update failed.
I had some network problem earlier today.
>> It's not clear whether this is the same annex referenced in target.c.
>
> Annexes are auxilliary data passed to target_xfer_partial:
> /* Request that OPS transfer up to LEN 8-bit bytes of the target's
> OBJECT. The OFFSET, for a seekable object, specifies the
> starting point. The ANNEX can be used to provide additional
> data-specific information to the target.
>
> For the remote protocol, this usually means qXfer packets, like so:
>
> `qXfer:OBJECT:read:ANNEX:OFFSET,LENGTH'
> Read uninterpreted bytes from the target's special data area
> identified by the keyword OBJECT. Request LENGTH bytes starting
> at OFFSET bytes into the data. The content and encoding of ANNEX
> is specific to the object; it can supply additional details about
> what data to access.
Thanks.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2007-06-23 21:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 18:01 Michael Eager
2007-06-23 18:57 ` Stan Shebs
2007-06-23 19:08 ` Michael Eager
2007-06-23 19:47 ` Eli Zaretskii
2007-06-23 20:51 ` Michael Eager
2007-06-23 21:23 ` Daniel Jacobowitz
2007-06-23 21:40 ` Michael Eager [this message]
2007-06-24 2:58 ` Eli Zaretskii
2007-06-24 4:32 ` Michael Eager
2007-06-25 18:03 ` Jim Blandy
2007-06-25 18:39 ` Michael Eager
2007-06-25 19:10 ` Jim Blandy
2007-06-25 19:26 ` Paul Koning
2007-06-25 19:32 ` Daniel Jacobowitz
2007-06-25 19:38 ` Robert Dewar
2007-06-25 19:48 ` Paul Koning
2007-06-25 20:09 ` Michael Eager
2007-06-25 20:40 ` Robert Dewar
2007-06-25 20:47 ` Robert Dewar
2007-06-25 20:31 ` Eli Zaretskii
2007-06-25 20:44 ` Robert Dewar
2007-06-25 21:00 ` Eli Zaretskii
2007-06-25 21:03 ` Robert Dewar
2007-06-25 21:06 ` Robert Dewar
2007-06-26 18:34 ` Markus Deuling
2007-06-26 18:36 ` Robert Dewar
2007-06-26 21:55 ` Jim Blandy
2007-06-26 22:14 ` Nick Roberts
2007-06-26 23:26 ` Robert Dewar
2007-06-26 23:39 ` Joel Brobecker
2007-06-26 23:43 ` Robert Dewar
2007-06-27 0:32 ` Jim Blandy
2007-06-27 0:42 ` Robert Dewar
2007-06-27 3:22 ` Eli Zaretskii
2007-06-27 0:23 ` Michael Eager
2007-06-25 20:42 ` Eli Zaretskii
2007-06-25 20:23 ` Eli Zaretskii
2007-06-25 21:52 ` Jim Blandy
2007-06-26 1:04 ` Paul Koning
2007-06-25 20:37 ` Eli Zaretskii
2007-06-25 20:15 ` 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=467D934C.10909@eagercon.com \
--to=eager@eagercon.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=stanshebs@earthlink.net \
/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