This is the mail archive of the
libc-hacker@sourceware.cygnus.com
mailing list for the glibc project.
Re: glibc2 & (de)register_frame_info
- To: cls@seawood.org (Christopher Seawood)
- Subject: Re: glibc2 & (de)register_frame_info
- From: hjl@lucon.org (H.J. Lu)
- Date: Tue, 2 Jun 1998 18:18:30 -0700 (PDT)
- Cc: libc-hacker@cygnus.com (GNU C Library)
>
> On Tue, 2 Jun 1998, H.J. Lu wrote:
>
> > You have a problem here. glibc 2.0.{6,7} shouldn't define
> > __register_frame_info nor __deregister_frame_info. Please
> > send me
> >
> > # nm /lib/libc-2.0.7.so | grep frame
> > # nm /lib/libc-2.0.6.so | grep frame
>
> Sorry, I should have been more precise. Libc itself does not define these
> symbols. However, the accompanying libraries do.
>
> [root@cseawood /lib]$ foreach n ( `ls *2.0.6*` )
> foreach? echo $n
> foreach? nm $n | grep register_frame_info
> foreach? end
> ld-2.0.6.so
> libBrokenLocale-2.0.6.so
> 00001030 T __deregister_frame_info
> 00000f44 T __register_frame_info
> 00000fbc T __register_frame_info_table
> libc-2.0.6.so
> libcrypt-2.0.6.so
> 00004290 T __deregister_frame_info
> 000041a4 T __register_frame_info
> 0000421c T __register_frame_info_table
I can see the problem now. libc.so has its own crtbeginS.o/crtendS.o
so that it doesn't have this problem. However it is not true for other
libraries in glibc 2.0. You have to compile glibc with the same
compiler you compile binaries.
--
H.J. Lu (hjl@gnu.org)