This is the mail archive of the
mailing list for the GCC project.
Re: __frame_state_for has dissappeared from libgcc
- To: Richard Henderson <rth at redhat dot com>, Mark Kettenis <kettenis at science dot uva dot nl>, gcc at gcc dot gnu dot org, libc-alpha at sources dot redhat dot com
- Subject: Re: __frame_state_for has dissappeared from libgcc
- From: Jakub Jelinek <jakub at redhat dot com>
- Date: Wed, 16 May 2001 23:26:11 +0200
- References: <200105162037.f4GKbfR06957@soliton.wins.uva.nl> <20010516140756.A25761@redhat.com>
- Reply-To: Jakub Jelinek <jakub at redhat dot com>
On Wed, May 16, 2001 at 02:07:56PM -0700, Richard Henderson wrote:
> On Wed, May 16, 2001 at 09:35:35PM +0200, Mark Kettenis wrote:
> > However contrary to the __eprintf-case, I expect that the removeal
> > of __frame_state_for from the shared libgcc will cause serious
> > problems, at least on GNU systems (the Hurd, Linux):
> Also unlike __eprintf, it was never intended that __frame_state_for be
> used outside of libgcc. That has been used is *extremely* irritating.
> This was brought to my attention a few days ago. I'm still pondering
> what to do about it. It may be possible to re-implement on top of the
> new EH code. It may be that glibc must grab the old code from gcc 2.95
> and include that in its source.
As I just wrote, the latter is not possible unless libgcc_s provides hooks
for it to find a fde corresponding to particular pc, because libgcc_s takes
over __register_frame_info & family of functions.