Hello,
Thank you both so much for the quick replies. Thank you for clarifying that
the expectation is to unconditionally traverse DIEs within a CU when looking
for a subprogram. I am currently working with some executables which have
large namespace sections that would be nice to skip over complet
When searching for addresses we first see if the compile unit's DW_AT_ranges
(or low/high pc) attribute contains the address we are looking for. Any CU that
doesn't contain the address doesn't need to have its child DIEs parsed, just
the top level DW_TAG_compile_unit DIE. Then we iterate over al
I suppose it didn't seem useful to provide ranges on namespaces. A C++
namespace isn't a program entity of its own, it's a way of managing names of
entities. It doesn't even restrict the scope of those names; you can refer to
them anywhere if you use the fully qualified version of the name. (Wit
Hello,
What is the reasoning for not including range information on
DW_TAG_namespace DIEs? Is there a canonical way to check if a
DW_TAG_namespace DIE contains a given address?
Thank you,
Jeremy
--
Dwarf-discuss mailing list
Dwarf-discuss@lists.dwarfstd.org
https://lists.dwarfstd.org/mailma
