OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

(Files): Document the possibility of loading unlinked object files.

This commit is contained in:
Eli Zaretskii 2005-06-18 12:36:06 +00:00
parent 638ac427cd
commit fc8be69e5e
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
gdb/doc/ChangeLog
View File

@ -6,6 +6,8 @@
(Output Formats): More detailed description of the `c' format.
(Memory): List explicitly all the formats supported by `x'.
(Threads): Add an @cindex entry for "thread apply".
(Files): Document the possibility of loading unlinked object
files.
2005-06-18 Nick Roberts <nickrob@snap.net.nz>

11
gdb/doc/gdb.texinfo
View File

@ -10651,6 +10651,17 @@ descriptions of the file options @samp{-mapped} and @samp{-readnow}
and with the commands @code{file}, @code{symbol-file}, or
@code{add-symbol-file}, described below), for more information.
@cindex unlinked object files
@cindex patching object files
You can load unlinked object @file{.o} files into @value{GDBN} using
the @code{file} command. You will not be able to ``run'' an object
file, but you can disassemble functions and inspect variables. Also,
if the underlying BFD functionality supports it, you could use
@kbd{gdb -write} to patch object files using this technique. Note
that @value{GDBN} can neither interpret nor modify relocations in this
case, so branches and some initialized variables will appear to go to
the wrong place. But this feature is still handy from time to time.
@item file
@code{file} with no argument makes @value{GDBN} discard any information it
has on both executable file and the symbol table.