From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3279 invoked by alias); 29 Oct 2007 20:40:58 -0000 Received: (qmail 3269 invoked by uid 22791); 29 Oct 2007 20:40:58 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 29 Oct 2007 20:40:55 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 82E7298348; Mon, 29 Oct 2007 20:40:53 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 567C698347; Mon, 29 Oct 2007 20:40:53 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1ImbPo-0000L7-DF; Mon, 29 Oct 2007 16:40:52 -0400 Date: Mon, 29 Oct 2007 20:40:00 -0000 From: Daniel Jacobowitz To: Ulrich Weigand Cc: gdb@sourceware.org Subject: Re: RFC: File transfer commands Message-ID: <20071029204052.GA875@caradoc.them.org> Mail-Followup-To: Ulrich Weigand , gdb@sourceware.org References: <20071029195510.GA18673@caradoc.them.org> <200710292029.l9TKTfow009984@d12av02.megacenter.de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710292029.l9TKTfow009984@d12av02.megacenter.de.ibm.com> User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-10/txt/msg00289.txt.bz2 On Mon, Oct 29, 2007 at 09:29:41PM +0100, Ulrich Weigand wrote: > Hmm, I'd have chosen to use a new target object (TARGET_OBJECT_FILE) > and corresponding qXfer packet; the "annex" would obviously be the > remote file name. > > However, that would not support unlink, and it would cause the > target to re-open the file for each access. That wouldn't matter > for my intended use scenario, not sure if it would in yours ... Yeah, I did think about using qXfer. Having to close and re-open the file isn't a problem for me either, but that didn't allow for other useful operations like delete. I haven't implemented any more operations than you see here, but it would be a reasonable addition to implement "remote ls" - and the corresponding MI commands, which might let us use a GUI file browser to select the target program to execute. I'd figured on retrieving remote shared libraries from memory, rather than from the filesystem; we don't need the contents, just the dynamic symbol table. But that wouldn't take advantage of unstripped libraries on the target with full symbols, so maybe the file would be useful too. -- Daniel Jacobowitz CodeSourcery