aboutsummaryrefslogtreecommitdiff
path: root/binutils/NEWS
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2019-02-25 12:15:41 +0000
committerNick Clifton <nickc@redhat.com>2019-02-25 12:15:41 +0000
commit39f0547e554df96608dd041d2a7b3c72882fd515 (patch)
tree53ca1f928e75345d1a9e3a409ef95ef9a2175304 /binutils/NEWS
parent60245a92ce2c16d0b43987c2442b1a125652b832 (diff)
downloadgdb-39f0547e554df96608dd041d2a7b3c72882fd515.zip
gdb-39f0547e554df96608dd041d2a7b3c72882fd515.tar.gz
gdb-39f0547e554df96608dd041d2a7b3c72882fd515.tar.bz2
Extend objdump's --dwarf=follow-links option so that separate debug info files will also be affected by other dump function, and symbol tables from separate debug info files will be used when disassembling the main file.
* objdump.c (sym_ok): New function. (find_symbol_for_address): Use new function. (disassemble_section): Compare sections by name, not pointer. (dump_dwarf): Move code to initialise byte_get pointer and iterate over separate debug files from here to ... (dump_bfd): ... here. Add parameter indicating that a separate debug info file is being dumped. For main file, pull in the symbol tables from all separate debug info files. (display_object): Update call to dump_bfd. * doc/binutils.texi: Document extened behaviour of the --dwarf=follow-links option. * NEWS: Mention this new feature. * testsuite/binutils-all/objdump.WK2: Update expected output. * testsuite/binutils-all/objdump.exp (test_follow_debuglink): Add options and dump file parameters. Add extra test. * testsuite/binutils-all/objdump.WK3: New file. * testsuite/binutils-all/readelf.exp: Change expected output for readelf -wKis test. * testsuite/binutils-all/readelf.wKis: New file.
Diffstat (limited to 'binutils/NEWS')
-rw-r--r--binutils/NEWS7
1 files changed, 7 insertions, 0 deletions
diff --git a/binutils/NEWS b/binutils/NEWS
index 5413321..7c9d7be 100644
--- a/binutils/NEWS
+++ b/binutils/NEWS
@@ -6,6 +6,13 @@
more than one are present in a file. (This usually happens when gcc's
-gsplit-dwarf option is used).
+ In addition objdump's --dwarf=follow-links now also affects its other
+ display options, so that for example, when combined with --syms it will
+ cause the symbol tables in any linked debug info files to also be
+ displayed. In addition when combined with --disassemble the --dwarf=
+ follow-links option will ensure that any symbol tables in the linked
+ files are read and used when disassembling code in the main file.
+
Changes in 2.32:
* The addr2line, c++filt, nm and objdump tools now have a limit on the