On Wed, Mar 10, 2021 at 10:07:27PM -0800, David Blaikie wrote: > On Wed, Mar 10, 2021 at 9:38 PM Jakub Jelinek <ja...@redhat.com> wrote: > > > On Wed, Mar 10, 2021 at 04:12:57PM -0800, David Blaikie via Dwarf-Discuss > > wrote: > > > On Wed, Mar 10, 2021 at 4:02 PM Cary Coutant <ccout...@gmail.com> wrote: > > > > > > > > > So in the end the logical thing to do when encountering a > > > > > > DW_FORM_rnglistx in a split-unit, in order to support everybody, is > > > > > > probably to go to the .debug_rnglists.dwo section, if there's one, > > > > > > disregarding the (inherited) DW_AT_rnglists_base. If there isn't, > > then > > > > > > try the linked file's .debug_rnglists section, using > > > > > > DW_AT_rnglists_base. If there isn't, then something is malformed. > > > > > > > > Looks reasonable to me. I think we need a new issue to clarify this in > > > > DWARF 6. > > > > > > > > > > Given that DWARFv5 isn't on by default in GCC yet & I think has a few > > more > > > > It is on by default. But -gstrict-dwarf is not on by default. > > > > Oh, it is - in a released version of the compiler, or only in development?
Still in development, but the prerelease already widely deployed by multiple Linux distributions. > & you're proposing changing the behavior only under -gstrict-dwarf, rather > than in general? Any particular reason? Just a typo, sorry, meant -gsplit-dwarf. Jakub _______________________________________________ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org