From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Remote file transfer support
Date: Fri, 30 Nov 2007 21:22:00 -0000 [thread overview]
Message-ID: <ufxyn1laq.fsf@gnu.org> (raw)
In-Reply-To: <20071130183650.GA16197@caradoc.them.org> (message from Daniel Jacobowitz on Fri, 30 Nov 2007 13:36:50 -0500)
> Date: Fri, 30 Nov 2007 13:36:50 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org
>
> Is this better?
>
> The @dfn{Host I/O} packets allow @value{GDBN} to perform I/O
> operations on the far side of a remote link. For example, Host I/O is
> used to upload and download files to a remote target with its own
> filesystem. Host I/O uses the same constant values and data structure
> layout as the target-initiated File-I/O protocol. However, the
> Host I/O packets are structured differently. The target-initiated
> protocol relies on target memory to store parameters and buffers.
> Host I/O requests are initiated by @value{GDBN}, and the
> target's memory is not involved. @xref{File-I/O Remote Protocol
> Extension}, for more details on the target-initiated protocol.
Yes, thanks.
> Here's my latest patch, which should correct all the problems you
> found. I also fixed cleanup when a write error occurs.
Thanks, the documentation patch is approved.
next prev parent reply other threads:[~2007-11-30 21:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 20:32 Daniel Jacobowitz
2007-10-31 21:35 ` Eli Zaretskii
2007-11-30 18:37 ` Daniel Jacobowitz
2007-11-30 21:22 ` Eli Zaretskii [this message]
2007-11-30 21:50 ` Daniel Jacobowitz
2007-12-01 4:10 ` Pedro Alves
2007-12-01 5:00 ` Daniel Jacobowitz
2007-12-03 9:51 ` Pierre Muller
2007-12-03 12:56 ` 'Daniel Jacobowitz'
2007-12-03 13:41 ` Pierre Muller
2007-12-16 21:54 ` 'Daniel Jacobowitz'
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=ufxyn1laq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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