From mboxrd@z Thu Jan 1 00:00:00 1970 From: hjl@lucon.org (H.J. Lu) To: law@cygnus.com Cc: gcc2@cygnus.com, egcs@cygnus.com Subject: Re: gcc 2.8.0 is broken on linux/x86 and more bug Date: Fri, 12 Dec 1997 01:52:00 -0000 Message-id: References: <17185.881913926@hurl.cygnus.com> X-SW-Source: 1997-12/msg00717.html > > I think that is what my patch does. It keeps the old name and > > appends _new to new interface. It seems to work for me. > I don't believe it handles the "free" issue correctly, then again, I'm > not real familiar with that code. > > Please explain to me how it works if both register_frame and > register_frame_new are are called by one program. > How does register_frame/register_frame_new get called? They are called by crtbegin.o/collect2. User doesn't use them directly. Since they are under our control, we always call the right one. My glibc.so calls register_frame. But the binaries generated by new egcs and gcc 2.8.0 call register_frame_new. In my environment register_frame/register_frame_new are mixed when libc.so is used. -- H.J. Lu (hjl@gnu.org)