Displaying 3 results from an estimated 3 matches for "form_addr_index".
2017 Nov 16
3
Collecting address ranges in DWARFUnit::collectAddressRanges.
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
2017 Nov 16
2
Collecting address ranges in DWARFUnit::collectAddressRanges.
...ess values are still in the .o file; but before that anything that's an
>> address really can't go into the DWO.
>>
>
> DWOs didn't exist (in a standard form) before DWARF 5, right? Insofar as
> they did exist (in a non-standard form) they have always supported
> FORM_addr_index to reference addresses in .debug_addr in the main .o.
>
> But the low_pc/high_pc/ranges attributes would appear in the .dwo, using a
> FORM_addr_index/FORM_addrx - so if you want to collect the address range of
> a CU you might need to load the .dwo to do so. That's the crux of what...
2018 Feb 09
0
Collecting address ranges in DWARFUnit::collectAddressRanges.
...; but before that anything
> that's an
> >> address really can't go into the DWO.
> >>
> >
> > DWOs didn't exist (in a standard form) before DWARF 5, right? Insofar as
> > they did exist (in a non-standard form) they have always supported
> > FORM_addr_index to reference addresses in .debug_addr in the main .o.
> >
> > But the low_pc/high_pc/ranges attributes would appear in the .dwo, using
> a
> > FORM_addr_index/FORM_addrx - so if you want to collect the address range
> of
> > a CU you might need to load the .dwo to do s...