[no HTML]
I had that before, and it didn't work, then I empirically changed to
next_cu_off because it contained the same offset I was supposed to get when I
compared to the libdwarf execution.
We already discarded the option of using dwarf_offdie_types since previously,
with libdwarf, it was p
I did not find the reference about the argument named next_cu_header_offset
(below I pasted the respective functions signatures).
Anyway, name orthography apart, what is being used in Dyninst with libdwarf is
exactly the value of what we called next_cu_off, which corresponds to the third
parame
On 03/17/2017 10:18 AM, SASHA NICOLAS DA ROCHA PINHEIRO wrote:
> I did not find the reference about the argument named
> next_cu_header_offset (below I pasted the respective functions
> signatures). Anyway, name orthography apart, what is being used in
> Dyninst with libdwarf is exactly the value o
https://sourceware.org/bugzilla/show_bug.cgi?id=21247
--- Comment #2 from Marat Radchenko ---
gimli was fixed ( https://github.com/gimli-rs/addr2line/pull/36 ) and now is
consistent with binutils (and llvm-symbolizer). I also sent a patch to
elftoolchain so it also resolves filename/lineno proper
