ubject: Re: [Dwarf-Discuss] The .debug_str_offsets section and
> libdwarf/dwarfdump
>
> On 04/16/2018 09:01 AM, David Blaikie wrote:
> > Adding a few folks working on Clang's DWARF5 functionality to see if
> > this is a known bug (David Anderson mentioned it may've c
On 04/16/2018 09:01 AM, David Blaikie wrote:
> Adding a few folks working on Clang's DWARF5 functionality to see if
> this is a known bug (David Anderson mentioned it may've come from
> Clang r327823) and/or has been fixed.
>
> Perhaps a minimal example that produces this behavior/bug would be
> us
Adding a few folks working on Clang's DWARF5 functionality to see if this
is a known bug (David Anderson mentioned it may've come from Clang r327823)
and/or has been fixed.
Perhaps a minimal example that produces this behavior/bug would be useful
for David to have (not sure if he wants/needs it if
Does your example have a DW_AT_producer string by chance?
On Sat, Apr 14, 2018 at 4:03 PM David Anderson via Dwarf-Discuss <
dwarf-discuss@lists.dwarfstd.org> wrote:
> I've just pushed a new version of libdwarf/dwarfdump to sourceforge.
> I mention this here because at least one compiler version
I've just pushed a new version of libdwarf/dwarfdump to sourceforge.
I mention this here because at least one compiler version is emitting
an incorrect .debug_str_offsets section (I believe).
You can get the source with
git clone git://git.code.sf.net/p/libdwarf/code
The new dwarfdump option
