Re: gcc 2.8.0 is broken on linux/x86 and more bug

[Jeffrey A Law <law at cygnus dot com>]

  In message <m0xgQ0h-0004ecC@ocean.lucon.org>you write:
  > > Furthermore, we must avoid calling "free" on any of the objects which
  > > come from static storage instead of malloc.  Thus, we have to keep track
  > > of which interface was used for each object so that we know whether or
  > > not its memory should be free'd.
  > > 
  > > The compiler should always emit calls to the new interfaces; the old
  > > interfaces would be for existing copies of ld.so which use the old
  > > interfaces.
  > > 
  > 
  > 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.  

jeff