From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Retrieve libraries from remote target
Date: Sat, 10 May 2008 17:22:00 -0000 [thread overview]
Message-ID: <utzh6le0g.fsf@gnu.org> (raw)
In-Reply-To: <200805092209.m49M9rWN000988@d12av02.megacenter.de.ibm.com>
> 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.
next prev parent reply other threads:[~2008-05-10 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 1:45 Ulrich Weigand
2008-05-09 1:47 ` Daniel Jacobowitz
2008-05-09 12:59 ` Eli Zaretskii
2008-05-09 23:58 ` Ulrich Weigand
2008-05-10 9:12 ` Eli Zaretskii
2008-05-10 12:48 ` Ulrich Weigand
2008-05-10 17:22 ` Eli Zaretskii [this message]
2008-05-11 22:20 ` Daniel Jacobowitz
2008-05-12 20:07 ` Eli Zaretskii
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=utzh6le0g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.com \
/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