This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: __register_frame_info and unwinding shared libraries
On Tue, Feb 15, 2005 at 09:41:22AM -0800, Richard Henderson wrote:
> On Tue, Feb 15, 2005 at 05:27:15PM +0000, Andrew Haley wrote:
> > So, now for my question: why do we not call __register_frame_info() or
> > __register_frame_info_bases() ?
>
> Because in the normal case for C/C++, folks don't use that many
> exceptions. So delaying doing anything until it's needed is a win.
>
> Obviously the normal case is different for Java.
>
> > We'd avoid a great many trips through
> > dl_iterate_phdr () and _Unwind_IteratePhdrCallback().
>
> 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.
This may be exactly what you're suggesting, but could we do this
instead of what we do now?
- Search the registered FDEs
- use dl_iterate_phdr to register and search any unregistered objects
--
Daniel Jacobowitz
CodeSourcery, LLC