Hi - > > We could then also introduce a new public function, dwarf_getdieranges > > (?) that does the new thing. But it doesn't have to be public on the > > first try as long as dwarf_addrdie and dwfl_module_addrdie work. (We > > might want to change the interface of dwarf_getdieranges so it can be > > "lazy" for example.) > > Ok this approach seems like the most flexible. Users can have both > .debug_aranges and CU-based aranges plus we don't have to change the > semantics of dwarf_getaranges. [...]
Another option is to generate the .debug_aranges automatically, but only if it is absent from the input dwarf file. (An eu-readelf user can tell if it was synthetic or not, if it matters.) - FChE
