[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/28029] debuginfod 2 tests UNTESTED
From: |
cvs-commit at gcc dot gnu.org |
Subject: |
[Bug binutils/28029] debuginfod 2 tests UNTESTED |
Date: |
Tue, 18 Jan 2022 00:57:14 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=28029
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot
gnu.org> ---
The master branch has been updated by Alan Modra <amodra@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e2c0149e8b0ce12accb8f4b02cbbeff3e91e4737
commit e2c0149e8b0ce12accb8f4b02cbbeff3e91e4737
Author: Alan Modra <amodra@gmail.com>
Date: Mon Nov 22 10:16:01 2021 +1030
PR28029, debuginfod tests
binutils/NEWS says of the change in --process-links semantics:
If other debug section display options are also enabled (eg
--debug-dump=info) then the contents of matching sections in both the
main
file and the separate debuginfo file *will* be displayed. This is
because in
most cases the debug section will only be present in one of the files.
Implying that debug info is dumped without --process-links. Indeed
that appears to be the case for readelf. This does the same for
objdump.
PR 28029
* objdump.c (dump_bfd): Do not exit early when !is_mainfile
&& !processlinks, instead just exclude non-debug output.
(dump_dwarf): Add is_mainfile parameter and pass to
dump_dwarf_section.
(dump_dwarf_section): Only display debug sections when
!is_mainfile and !process_links.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/28029] debuginfod 2 tests UNTESTED,
cvs-commit at gcc dot gnu.org <=