From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32054 invoked by alias); 10 May 2008 09:12:05 -0000 Received: (qmail 32044 invoked by uid 22791); 10 May 2008 09:12:04 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout3.012.net.il (HELO mtaout3.012.net.il) (84.95.2.7) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 10 May 2008 09:11:45 +0000 Received: from HOME-C4E4A596F7 ([83.130.255.47]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K0N00434BJMPEN0@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Sat, 10 May 2008 12:26:10 +0300 (IDT) Date: Sat, 10 May 2008 17:22:00 -0000 From: Eli Zaretskii Subject: Re: [rfc] Retrieve libraries from remote target In-reply-to: <200805092209.m49M9rWN000988@d12av02.megacenter.de.ibm.com> X-012-Sender: halo1@inter.net.il To: Ulrich Weigand Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: References: <200805092209.m49M9rWN000988@d12av02.megacenter.de.ibm.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-05/txt/msg00336.txt.bz2 > Date: Sat, 10 May 2008 00:09:53 +0200 (CEST) > From: "Ulrich Weigand" > Cc: gdb-patches@sourceware.org > > Eli Zaretskii wrote: > > > Date: Fri, 9 May 2008 21:28:46 +0200 (CEST) > > > From: "Ulrich Weigand" > > > Cc: gdb-patches@sourceware.org > > > > > > > > The user interface is simple: if the path specified as "sysroot" starts > > > > > with the string "remote:", the sysroot location is assumed to be on the > > > > > remote target. > > > > > > > > What if my _local_ "sysroot" happens to begin with the literal string > > > > "remote:"? How can I tell GDB this is not a remote location? > > > > > > You cannot. Is this limitation a real problem? > > > > If it can happen in real usage, then I think it's a real problem. > > Well, in real usage the sysroot tends to be specified as absolute > path, so that problem cannot occur. If you do want to specify the > sysroot as relative path, there typically are multiple ways to > identify the same directory, e.g. on Unix you could always use > "./remote:" instead of "remote:" ... (I am not 100% certain that > something like that is possible on any host OS supported by GDB.) > > But I'm certainly open to alternative interfaces. Do you have > suggestions for a different approach? If "./remote:" will work, I'm fine with that; we just need to mention that in the manual. Can we verify that "./remote:" will work with sysroot? Failing that, some kind of escape-protecting the colon will do.