From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: [remote] RFC: Replace qPart with qXfer
Date: Thu, 22 Jun 2006 09:05:00 -0000 [thread overview]
Message-ID: <e7dl4a$j6i$1@sea.gmane.org> (raw)
In-Reply-To: <20060622031731.GA26722@nevyn.them.org>
Daniel Jacobowitz wrote:
> `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.
Why do we need OBJECT+ANNEX addressing and opposed to just OBJECT? If
'OBJECT' is just a string, can't we push anything in it, without needed
extra level of addressing?
- Volodya
next prev parent reply other threads:[~2006-06-22 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 8:42 Daniel Jacobowitz
2006-06-22 9:05 ` Vladimir Prus [this message]
2006-06-22 12:35 ` What's the difference between gdb arm targets? Dave Murphy
2006-06-22 12:39 ` Daniel Jacobowitz
2006-06-22 13:17 ` [remote] RFC: Replace qPart with qXfer Daniel Jacobowitz
2006-06-23 16:23 ` Eli Zaretskii
2006-06-23 18:06 ` Daniel Jacobowitz
2006-06-23 20:10 ` Eli Zaretskii
2006-06-24 2:24 ` Daniel Jacobowitz
2006-06-25 3:10 ` Karl Berry
2006-06-25 4:07 ` 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='e7dl4a$j6i$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb@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