Undefined __register_frame_info problem
Jeffrey A Law
law@cygnus.com
Sun May 3 23:10:00 GMT 1998
In message <199804272338.QAA17216@trill.cisco.com>you write:
> > Now if this were the case wouldn't I find a symbol in one of the
> > libraries that had a was unresolved __register_proc_info when I did an
> > nm?
> >
> > I would assume so.
>
> The reason that I pointed that out was that nm'd every shared library
> on my system and __register_proc_info was not found in any of them. So
> I couldn't see where I was getting the unresolved reference.
Note we're looking for __register_frame_info, not register_proc_info.
> I took the chance and compiled up glibc with egcs stuck it in
> /usr/local and now as long as I put /usr/local/lib in my
> LD_LIBRARY_PATH, I have no problem. There don't seem to be any
> problems with utilities that were compiled with before this. That is
> what I was worried about.
That may or may not actually be the root of the problem. Good to
know for a workaround though.
Can you look at these two files to see if they reference
__register_frame_info as an undefined symbol?
They're particularly interesting because they appear after
-lgcc on the command line gcc builds for the linker (based on
the -Wl,-v -Wl,-t output you sent).
/usr/local/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.90.27/crtend.o
/usr/local/lib/crtn.o
jeff
More information about the Gcc-bugs
mailing list