This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] Retrieve libraries from remote target
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Ulrich Weigand <uweigand at de dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 10 May 2008 12:11:43 +0300
- Subject: Re: [rfc] Retrieve libraries from remote target
- References: <200805092209.m49M9rWN000988@d12av02.megacenter.de.ibm.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 10 May 2008 00:09:53 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> Cc: gdb-patches@sourceware.org
>
> Eli Zaretskii wrote:
> > > Date: Fri, 9 May 2008 21:28:46 +0200 (CEST)
> > > From: "Ulrich Weigand" <uweigand@de.ibm.com>
> > > 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.