[llvm-dev] Collecting address ranges in DWARFUnit::collectAddressRanges.
Robinson, Paul via llvm-dev
llvm-dev at lists.llvm.org
Thu Nov 16 11:44:53 PST 2017
There's no requirement that DW_AT_ranges (or high/low_pc) appear on the skeleton CU rather than the DWO CU. So it's quite possible that to get the address ranges covered by the CU one would need to look in the DWO, I think?
Is that not correct/have I misunderstood something there?
The DWO isn't supposed to contain addresses (because it isn't supposed to contain relocations). In DWARF 5 the DWO can have FORM_addrx references to the .debug_addr section in the main .o file, which allows the DWO to contain DIEs/attributes that should have address values, because the actual address values are still in the .o file; but before that anything that's an address really can't go into the DWO.
Unless I am also misunderstanding something…
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev