Re: DWARF EH for PPC

[Dale Scheetz <dwarf@polaris.net>]

On Tue, 8 Dec 1998, H.J. Lu wrote:

> > > > > You must be running glibc 2.0, which exports the register_frame suff
> > > > > in libc.so by accident. We fix it in glibc 2.1 so that the
> > > 
> > > I meant to say libm.so.
> > > 
> > > > > register_frame stuff will be in libstdc++.so.
> > > > 
> > > > But it doesn't.  libm did for a while in 2.0.7u, but that got fixed
> > > > (and caused a nasty screwup)...
> > > > 
> > > > 
> > > 
> > > libstdc++.so is linked with both libc.so and libm.so.
> > 
> > And libm did export register_frame_info for a while, and caused
> > libstdc++ nightmares; but now it doesn't, any more.  So libstdc++
> > doesn't, any more.  Should it?
> > 
> 
> As far as I know, libm.so in glibc 2.0.7 still exports register_frame:

The Debian release called 2.0.7u was constructed from the 2.0.7-pre6
tarballs and originally had the __register_frame_info symbol defined in
libm. Starting with release 2.0.7u-6 this symbol was removed using the
patch that was applied to the 2.1 pre-release.

This was done because programs built against this version of 2.0.7 would
not run on systems with previous versions of the 2.0.7 line installed, nor
would they run on other distributions with a previous 2.0.7.

Programs compiled against the -6, patched Debian version will run against
any of the previous releases of the 2.0.7 line.

We are still recovering from the repercussions of this change. Only
2.0.7-pre6 introduced this change. It was my understanding that it was a
mistake and would, eventually, be fixed.

Waiting is, 

Dwarf
--
_-_-_-_-_-   Author of "The Debian Linux User's Guide"  _-_-_-_-_-_-

aka   Dale Scheetz                   Phone:   1 (850) 656-9769
      Flexible Software              11000 McCrackin Road
      e-mail:  dwarf@polaris.net     Tallahassee, FL  32308

_-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_-