Re: __register_frame_info and unwinding shared libraries

[Andrew Haley <aph at redhat dot com>]

Jakub Jelinek writes:

 > >  > While I still like using dl_iterate_phdr instead of
 > >  > __register_frame_info_bases for totally aesthetic reasons, there
 > >  > have been changes made to the dl_iterate_phdr interface since the
 > >  > gcc support was written that would allow the dl_iterate_phdr
 > >  > results to be cached.
 > > 
 > > That would be nice.  Also, we could fairly easily build a tree of
 > > nodes, one for each loaded object, then we wouldn't be doing a linear
 > > search through them.  We could do that lazily, so it wouldn't kick in
 > > 'til needed.
 > 
 > Here is a rough patch for what you can do.

Thanks very much.  I'm working on it.

Andrew.