From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-52474-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 14437 invoked by alias); 30 Nov 2007 21:22:11 -0000
Received: (qmail 14429 invoked by uid 22791); 30 Nov 2007 21:22:10 -0000
X-Spam-Check-By: sourceware.org
Received: from heller.inter.net.il (HELO heller.inter.net.il) (213.8.233.23)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 30 Nov 2007 21:22:04 +0000
Received: from HOME-C4E4A596F7 (IGLD-83-130-220-201.inter.net.il [83.130.220.201]) 	by heller.inter.net.il (MOS 3.7.3a-GA) 	with ESMTP id EGH92443 (AUTH halo1); 	Fri, 30 Nov 2007 23:21:49 +0200 (IST)
Date: Fri, 30 Nov 2007 21:22:00 -0000
Message-Id: <ufxyn1laq.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
CC: gdb-patches@sourceware.org
In-reply-to: <20071130183650.GA16197@caradoc.them.org> (message from Daniel 	Jacobowitz on Fri, 30 Nov 2007 13:36:50 -0500)
Subject: Re: [rfc] Remote file transfer support
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <20071029203042.GA26597@caradoc.them.org> <u4pg7qaq6.fsf@gnu.org> <20071130183650.GA16197@caradoc.them.org>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2007-11/txt/msg00570.txt.bz2

> 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.