This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfa] Rename "set solib-absolute-prefix" to "set sysroot", improve docs
- From: Daniel Jacobowitz <drow at false dot org>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 5 Jan 2007 14:20:42 -0500
- Subject: Re: [rfa] Rename "set solib-absolute-prefix" to "set sysroot", improve docs
- References: <20070105174507.GA31679@nevyn.them.org> <u4pr51es2.fsf@gnu.org>
On Fri, Jan 05, 2007 at 08:58:53PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 5 Jan 2007 12:45:07 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Eli Zaretskii <eliz@gnu.org>
> >
> > 2007-01-05 Daniel Jacobowitz <dan@codesourcery.com>
> >
> > * gdb.texinfo (Commands to specify files): Describe
> > "set sysroot" and "show sysroot".
> > (Using the `gdbserver' program): Lowercase argument
> > to @var. Expand description of setting up GDB on the
> > host.
>
> Fine with me, but:
>
> > +@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.
> 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?
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.
--
Daniel Jacobowitz
CodeSourcery