This is the mail archive of the
dwarf2@corp.sgi.com
mailing list for the dwarf2 project.
Re: Requested PROPOSAL(S) regarding multisection location and ranges lists
>>>>> "Michael" == Michael Eager <eager@eagercon.com> writes:
> Jason Merrill wrote:
>>
>> It seems unreasonably redundant to have:
>>
>> A list of address ranges in .debug_aranges
>> A list of address ranges in AT_ranges
>> A list of address range beginnings in AT_base_addresses
>>
>> What was the problem with just using .debug_aranges, again?
> .debug_aranges is an optional section. Previous proposals would
> have changed it into a required section. It was the general opinion
> that the location lists in the main body of the Dwarf 2 data should
> be complete, not split between the .debug and .debug_aranges sections.
Do you mean .debug_loc and .debug_aranges?
I have trouble seeing why the advantage of putting everything related to
location lists in a single section outweighs the disadvantage of having two
(or three) copies of exactly the same information, especially since they
would be accessed through two different pointers in the CU DIE anyway. Why
not just make DW_AT_ranges point into .debug_aranges?
Jason