This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: Problems with exception handling in glibc and gcc.
Jason Merrill <jason@redhat.com> writes:
|> Geoff Keating <geoffk@cygnus.com> writes:
|>
|> > > We should have learned the lesson when last time we did it in Dec.
|> > > 1997. We had a lengthy discussion then. I am not sure if any messages
|> >
|> > It's happened several times since. It's quite annoying. Perhaps we
|> > could put a comment in there to stop this happening?
|>
|> No. These interfaces are internal to libgcc and should not be
|> restricted. The proper fix is to stop exporting these functions from
|> glibc. There's no reason to do that. Really, there's no reason for
|> them to be in glibc at all, but at the very least they should be
|> hidden.
How do you make sure that `static struct object *objects' from
frame-dwarf2.c is unique in the complete program, including all shared
objects?
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg