This is the mail archive of the
libc-hacker@sourceware.cygnus.com
mailing list for the glibc project.
glibc2 & (de)register_frame_info
- To: egcs@cygnus.com, libc-alpha@gnu.org
- Subject: glibc2 & (de)register_frame_info
- From: Christopher Seawood <cls@seawood.org>
- Date: Tue, 2 Jun 1998 12:11:54 -0700 (PDT)
- Reply-To: Christopher Seawood <cls@seawood.org>
When I compile glibc 2.0.{6,7} with egcs, glibc ends up defining
the symbols __register_frame_info & __deregister_frame_info. I noticed
that these are also defined in egcs' libgcc.a Should this be happening?
The real problem happens when I upgrade to a glibc that was not built with
egcs. Some of the programs I compiled with egcs under a egcs built glibc
also have a dependency on these symbols. If it wasn't /bin/login, I might
not have cared so much. :-/
I have a box at home running RedHat's glibc 2.0.7-7 rpm and one at work
running glibc 2.0.6 compiled with egcs 1.0.1 (maybe 1.0.2). Both boxes
have egcs 1.0.3a installed. I recompiled the util-linux 2.7-15 srpm on
both boxes. At work, __register_frame_info turns up when I strings
/bin/login. At home, it does not.
- cls