This is the mail archive of the elfutils-devel@sourceware.org mailing list for the elfutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Using dwfl to enumerate frames of current thread


Mark Wielaard <mjw@redhat.com> writes:

> And this is the problem. Sorry. I should have realized earlier.
> We use the .debug_aranges to get a quick index of the CUs and which
> address ranges they cover. In the case that there is no .debug_aranges
> we could do a full scan of all CUs. But that is somewhat inefficient,
> since no .debug_aranges could also mean that there really are no
> CUs with address scope DIEs (however that is probably unlikely). But
> if there is a .debug_aranges then we do assume it is complete. I am
> thinking whether we should still scan all CUs anyway if we are
> looking for an address that is really inside a module. But I think
> that would quickly become very inefficient.
>
Does elfutils need .debug_ranges as well?

Cheers,

- Ben

Attachment: signature.asc
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]