Andrew Haley writes:
> 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 writte
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
On Tue, Feb 15, 2005 at 06:02:39PM +, Andrew Haley wrote:
> Richard Henderson writes:
> > On Tue, Feb 15, 2005 at 05:27:15PM +, Andrew Haley wrote:
> > > So, now for my question: why do we not call __register_frame_info() or
> > > __register_frame_info_bases() ?
> >
> > Because in the
Richard Henderson writes:
> On Tue, Feb 15, 2005 at 05:27:15PM +, 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 dela
On Tue, Feb 15, 2005 at 12:43:44PM -0500, Daniel Jacobowitz wrote:
> This may be exactly what you're suggesting, but could we do this
> instead of what we do now?
>
> - use dl_iterate_phdr to register and search any unregistered objects
Done naievely, this will fail with dlclose.
r~
On Tue, Feb 15, 2005 at 09:41:22AM -0800, Richard Henderson wrote:
> On Tue, Feb 15, 2005 at 05:27:15PM +, 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 us
On Tue, Feb 15, 2005 at 05:27:15PM +, 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 w
This is about DWARF 2 unwinding through shared libraries.
As far as I can see, on current x86 GNU/Linux targets we don't call
__register_frame_info() or __register_frame_info_bases() from the
library startup code in crtbegin. There is code to do it, but it's
disabled.
When _Unwind_Find_FDE() is
