aboutsummaryrefslogtreecommitdiff
path: root/binutils/doc
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2008-02-26 08:44:10 +0000
committerNick Clifton <nickc@redhat.com>2008-02-26 08:44:10 +0000
commit3276085244458aabe070c7975b052af343d7f59c (patch)
tree4ebbb775fc2241120b25bd1b601f51f19099631c /binutils/doc
parent625af618e73144b15dcb1ff188ce91439ec4bd5b (diff)
downloadgdb-3276085244458aabe070c7975b052af343d7f59c.zip
gdb-3276085244458aabe070c7975b052af343d7f59c.tar.gz
gdb-3276085244458aabe070c7975b052af343d7f59c.tar.bz2
* objdump.c (objdump_print_addr): If displaying file offsets, show
the offset even if there are no symbols available. (dump_section): Display nothing if none of the section is going to be dumped. Display the file offset, if requested, of the location from where the dump starts. * doc/binutils.texi (objdump): Mention that dumping via the -s switch is also affected by the -F option.
Diffstat (limited to 'binutils/doc')
-rw-r--r--binutils/doc/binutils.texi3
1 files changed, 2 insertions, 1 deletions
diff --git a/binutils/doc/binutils.texi b/binutils/doc/binutils.texi
index e7d4dd1..43e7509 100644
--- a/binutils/doc/binutils.texi
+++ b/binutils/doc/binutils.texi
@@ -1723,7 +1723,8 @@ When disassembling sections, whenever a symbol is displayed, also
display the file offset of the region of data that is about to be
dumped. If zeroes are being skipped, then when disassembly resumes,
tell the user how many zeroes were skipped and the file offset of the
-location from where the disassembly resumes.
+location from where the disassembly resumes. When dumping sections,
+display the file offset of the location from where the dump starts.
@item --file-start-context
@cindex source code context