bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/27387] [readelf] Support -ggdb3 -gsplit-dwarf output


From: vries at gcc dot gnu.org
Subject: [Bug binutils/27387] [readelf] Support -ggdb3 -gsplit-dwarf output
Date: Fri, 26 Feb 2021 14:39:57 +0000

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

--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Nick Clifton from comment #7)
> (In reply to Nick Clifton from comment #6)
> 
> > Quick question: do you know where I can find the definition of the
> > contents of a .debug_macro.dwo section in the DWARF standard ?   
> 
> Naturally as soon as I posted this question I found the answer.  Section
> 6.3.1.
> 

Heh :)

> But this does lead to the question - why are the version numbers 0 amd 1
> seen in some of the .debug_macro.dwo sections ?  According to section 7.23
> paragraph 1 of the DWARF-5 spec, the version number should always be 5.

Yeah, I see that too.

If I do:
...
$ gcc hello.c -ggdb3 -gsplit-dwarf -save-temps -dA
...
and then grep:
...
$ grep -A2 debug_macro.dwo hello.s
...
I just get these type of entries:
...
        .section        .debug_macro.dwo,"e",@progbits
.Ldebug_macro0:
        .value  0x4     # DWARF macro version number
--
        .section       
.debug_macro.dwo,"G",@progbits,wm4.stdcpredef.h.19.006d14bbbe0dc07ba9b1ce3fdc8e40d3,comdat
.Ldebug_macro1:
        .value  0x4     # DWARF macro version number
--
...

So it this an assembler bug then?

-- 
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]