yggdrasil/binutils-gdb
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Document "target:" sysroot changes

Browse Source 
This commit documents the newly added "target:" sysroot feature.

gdb/ChangeLog:

	* NEWS: Announce the new default sysroot of "target:".

gdb/doc/ChangeLog:

	* gdb.texinfo (set sysroot): Document "target:".
This commit is contained in:
Gary Benson 2015-04-02 13:38:29 +01:00
parent fed040c6a5
commit 599bd15cda
4 changed files with 29 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/ChangeLog
View File

@ -1,3 +1,7 @@
2015-04-02 Gary Benson <gbenson@redhat.com>
* NEWS: Announce the new default sysroot of "target:".
2015-04-02 Gary Benson <gbenson@redhat.com>
* main.c (captured_main): Set gdb_sysroot to "target:"

7
gdb/NEWS
View File

@ -24,6 +24,13 @@
present in the debug info. This typically includes the compiler version
and may include things like its command line arguments.
* Directory names supplied to the "set sysroot" commands may be
prefixed with "target:" to tell GDB to access shared libraries from
the target system, be it local or remote. This replaces the prefix
"remote:". The default sysroot has been changed from "" to
"target:". "remote:" is automatically converted to "target:" for
backward compatibility.
* Python Scripting
** gdb.Objfile objects have a new attribute "username",

4
gdb/doc/ChangeLog
View File

@ -1,3 +1,7 @@
2015-04-02 Gary Benson <gbenson@redhat.com>
* gdb.texinfo (set sysroot): Document "target:".
2015-04-01 Sasha Smundak <asmundak@google.com>
* doc/python.texi (Writing a Frame Unwinder in Python): Add

23
gdb/doc/gdb.texinfo
View File

@ -17854,15 +17854,20 @@ libraries, they need to be laid out in the same way that they are on
the target, with e.g.@: a @file{/lib} and @file{/usr/lib} hierarchy
under @var{path}.
If @var{path} starts with the sequence @file{remote:}, @value{GDBN} will
retrieve the target libraries from the remote system. This is only
supported when using a remote target that supports the @code{remote get}
command (@pxref{File Transfer,,Sending files to a remote system}).
The part of @var{path} following the initial @file{remote:}
(if present) is used as system root prefix on the remote file system.
@footnote{If you want to specify a local system root using a directory
that happens to be named @file{remote:}, you need to use some equivalent
variant of the name like @file{./remote:}.}
If @var{path} starts with the sequence @file{target:} and the target
system is remote then @value{GDBN} will retrieve the target binaries
from the remote system. This is only supported when using a remote
target that supports the @code{remote get} command (@pxref{File
Transfer,,Sending files to a remote system}). The part of @var{path}
following the initial @file{target:} (if present) is used as system
root prefix on the remote file system. If @var{path} starts with the
sequence @file{remote:} this is converted to the sequence
@file{target:} by @code{set sysroot}@footnote{Historically the
functionality to retrieve binaries from the remote system was
provided by prefixing @var{path} with @file{remote:}}. If you want
to specify a local system root using a directory that happens to be
named @file{target:} or @file{remote:}, you need to use some
equivalent variant of the name like @file{./target:}.
For targets with an MS-DOS based filesystem, such as MS-Windows and
SymbianOS, @value{GDBN} tries prefixing a few variants of the target