This is the mail archive of the
archer@sourceware.org
mailing list for the Archer project.
Re: Initial psymtab replacement results
> I don't think so, or at least, I couldn't think of anything. Our
> current branches, including F12, check for a known GCC bug, but
> otherwise assume that if aranges exists, it is correct.
FWIW, elfutils (libdw) does use it and rely on its correctness for
address->CU lookups. But that direction of lookup is only used in
eu-addr2line and in systemtap's rarely-used numeric address probe syntax.
> There's also an issue with knowing whether it is actually complete; I
> didn't think of this until relatively recently:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42288
I think we discussed this before and I've forgotten again why that issue
matters. In the status quo there is a .debug_aranges hunk for each CU from
the beginning of the existing of the corresponding .debug_info hunk at
compile time, and that can never be "stripped" except by strip et al
that remove .debug_info along with it.
> I think this question is related to Keith's work on avoiding
> DW_AT_MIPS_linkage_name. I think the current answer is that there are
> some known missing DWARF features relating to C++. However, Keith and
> Dodji have worked on GNU extensions for at least some of these.
I take this to mean a verification of my supposition that .debug_pub*
indeed are not a generic extraction from the DIE tree as things stand.
Thanks,
Roland