[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name i
From: |
dblaikie at gmail dot com |
Subject: |
[Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang |
Date: |
Sat, 27 Aug 2022 01:26:53 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=29529
--- Comment #1 from David Blaikie <dblaikie at gmail dot com> ---
So DWARFv5 added a zeroth entry to the line table (used to be the line table
started at 1).
GCC produces two entries even for a simple file - a zeroth and a first, both
with the same value, and GCC always use the first.
Clang produces one entry and uses that.
Looks like objdump is ignoring/marking the zeroth as "unknown" - if you add a
#line to the source so that Clang uses that as a first entry (after the zeroth
original entry) then objdump behaves fine.
So, yeah, missing zeroth entry in DWARFv5 (now that it has zeroth entries)
somewhere in objdump.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/29529] New: [objdump] -l flag can't parse -gdwarf-5 file name info from clang, ndesaulniers at google dot com, 2022/08/26
- [Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang, ndesaulniers at google dot com, 2022/08/26
- [Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang,
dblaikie at gmail dot com <=
- [Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang, nickc at redhat dot com, 2022/08/30
- [Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang, cvs-commit at gcc dot gnu.org, 2022/08/30
- [Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang, nickc at redhat dot com, 2022/08/30
- [Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang, ndesaulniers at google dot com, 2022/08/30