This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/20645] Build with "-fdebug-types-section" -> Dwarf Error: wrong version in compilation unit header
- From: "internet at 123gen dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 29 Sep 2016 19:42:11 +0000
- Subject: [Bug gdb/20645] Build with "-fdebug-types-section" -> Dwarf Error: wrong version in compilation unit header
- Auto-submitted: auto-generated
- References: <bug-20645-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20645
--- Comment #1 from Zouzou <internet at 123gen dot com> ---
I went through the relevant gdb/dwarf2read.c code as well as COFF handlers in
bfd/ but couldn't spot anything obvious, though I did see a few "fixme"s here
and there in bfd/...
Running "objdump --dwarf=info test.exe" also shows errors:
objdump: Warning: Invalid pointer size (0) in compunit header, using 4
instead
objdump: Warning: Debug info is corrupted, length of CU at 53 extends
beyond end of section (length = 5300)
Attached, the output of "objdump --dwarf=info" on a regular program (built with
"-g" only) and on the same program built with the .debug_types section.
(Only the .debug_types one produces the above messages.)
I still don't know where the blame lies though; could be in the way GDB /
objdump parse the data and could also be in the way GCC emits it.
Should I report this on the GCC tracker?
Thanks
--
You are receiving this mail because:
You are on the CC list for the bug.