Undefined __register_frame_info problem
Jeffrey A Law
Wed Apr 22 22:35:00 GMT 1998
In message < 199804221045.DAA32249@trill.cisco.com >you write:
> That doesn't seem to be the case. All the programs on my system that
> exhibit this problem do not use any shared libraries except for those
> included within glibc which was installed on the system as a update
> from redhat. I do not know what compiler glibc was compiled with but
> the libcc.a that came with it does not contain the
> __register_frame_info symbol.
Note that ld.so (the dynamic linker) is effectively a shared library,
so you might be using shared libraries and not even known it.
> [bwoodard@trill fetchmail-4.4.1]$ nm /usr/lib/gcc-lib/i386-redhat-linux/2.7
> .2.3/libgcc.a | grep __register_frame_info
Right. __register_frame_info should not be in a 2.7 based library.
> and so I believe that I am linking against the right version of
> libgcc.a. Could it be a problem with what linker egcs is calling at
> certain times because this looks a bit strange:
Unlikely -- the behavior of egcs "ld" calling back to /usr/bin/ld
is exactly what we expect. The "egcs ld" is actually just a
front end to the system linker.
It might be wise to use -Wl,-v -Wl,-t on the link line to try and
get more debugging information from the linker.
More information about the Gcc-bugs