From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: RFC: File transfer commands
Date: Mon, 29 Oct 2007 23:54:00 -0000 [thread overview]
Message-ID: <20071029235427.GA11949@caradoc.them.org> (raw)
In-Reply-To: <4053daab0710291639h36a1f976rbc3fc611337852@mail.gmail.com>
On Mon, Oct 29, 2007 at 11:39:15PM +0000, Pedro Alves wrote:
> > Are these the right commands for it?
> Did you consider reusing the file-I/O remote protocol extension (with
> host/target reversed)?
> http://sourceware.org/gdb/current/onlinedocs/gdb_33.html#SEC681
I stayed as close to it as I could manage. The differences are
unavoidable, though, because the File I/O bits store pathnames as
address/length pairs in target memory. It's too silly (and sometimes
too hard) to poke a filename into target memory just so the debug
server can open it.
My first draft used the same Fopen, Fwrite, etc. packets as the
File I/O bits. Eventually I realized that that assigned two
conflicting meanings to the F packet. If I'd tried it on a
stub that supported both it would have gotten really hairy.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-10-29 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 19:55 Daniel Jacobowitz
2007-10-29 20:29 ` Ulrich Weigand
2007-10-29 20:40 ` Daniel Jacobowitz
2007-10-30 18:29 ` Jim Blandy
2007-10-30 18:41 ` Daniel Jacobowitz
2007-11-01 0:24 ` Jim Blandy
2007-10-29 23:39 ` Pedro Alves
2007-10-29 23:54 ` Daniel Jacobowitz [this message]
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=20071029235427.GA11949@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).