Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfa] Rename "set solib-absolute-prefix" to "set sysroot", improve docs
Date: Sat, 06 Jan 2007 10:32:00 -0000	[thread overview]
Message-ID: <uwt40zbrx.fsf@gnu.org> (raw)
In-Reply-To: <20070105192042.GB1031@nevyn.them.org> (message from Daniel 	Jacobowitz on Fri, 5 Jan 2007 14:20:42 -0500)

> Date: Fri, 5 Jan 2007 14:20:42 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org
> > 
> > > +@item set sysroot @var{path}
> > > +If this variable is set, @value{GDBN} will use @var{path} as the
> > 
> > The "set" commands don't set variables, at least we don't usually
> > explain them like that.
> 
> So just delete the first clause, and use this for the intro sentence?
> 
>   Use @var{path} as the system root for the program being debugged.

Yes.

> > Btw, what would this command do for Windows-style C:/foo/bar file
> > names?  Would it work as users expect?
> 
> Using a Windows path as the system root, to cross debug a Unix target,
> will work fine.  It won't do anything especially sensible if you try to
> apply a system root to Windows full paths, I'm afraid - the same is
> true for sysroots in GCC, and I don't even know what I'd expect it to
> do.  Probably /sysroot/c/foo/bar?

Either that, or strip the drive letter from the original file name and
append the rest to the value of sysroot.

> If someone wants to add Windows support I'd be happy to review patches,
> but I don't believe a Windows targeted GDB will reach this code.

If no one needs that now, we don't need to bother.


  reply	other threads:[~2007-01-06 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 17:45 Daniel Jacobowitz
2007-01-05 18:59 ` Eli Zaretskii
2007-01-05 19:20   ` Daniel Jacobowitz
2007-01-06 10:32     ` Eli Zaretskii [this message]
2007-01-08 19:00       ` Daniel Jacobowitz

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=uwt40zbrx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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