bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/30355] New: [DWARFv5] readelf: loc_offset XX too big


From: ndesaulniers at google dot com
Subject: [Bug binutils/30355] New: [DWARFv5] readelf: loc_offset XX too big
Date: Fri, 14 Apr 2023 17:34:57 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=30355

            Bug ID: 30355
           Summary: [DWARFv5] readelf: loc_offset XX too big
           Product: binutils
           Version: 2.40
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: ndesaulniers at google dot com
  Target Milestone: ---

When running readelf on a Linux kernel built with clang with
DEBUG_INFO_DWARF5=y and CONFIG_LTO_CLANG_FULL=y, I get a stream of warnings
related to loc_offset that I wasn't able to reproduce with llvm-dwarfdump. 
This could be perhaps a bug in clang's encoding of loc_offset, but might also
be an issue in GNU readelf, or perhaps even somewhere else.

$ /usr/bin/readelf --debug-dump=info vmlinux 1>/dev/null
readelf: Warning: loc_offset 78 too big
...

even with an allnoconfig kernel with the above two configs re-enabled, the
resulting vmlinux size is 34M in size; probably too large to attach here?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]