[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#27334: libc resolver problem solved (critical bug)



On Wed, 18 Nov 1998, Dale Scheetz wrote:

> On Wed, 18 Nov 1998, Gergely Madarasz wrote:
> 
> > On Wed, 18 Nov 1998, Dale Scheetz wrote:
> > 
> > > How did you decide that the library was compiled with egcs? I don't have
> > > egcs installed, and, to the best of my knowledge, this release was
> > > compiled using gcc 2.7.2.3.
> > 
> > 2.0.7u-5 downloaded from ftp.de.debian.org:
> > 
> > gorgo@lovi:~$ strings /lib/libc.so.6 | grep Compiled
> > Compiled by GNU CC version egcs-2.90.27 980315 (egcs-1.0.2 release).
> > Compiled on a Linux 2.0.33 system on 1998/11/09.
> 
> Well, I found the problem. While dpkg reported gcc installed and egcs not
> installed, there was a copy of gcc in /usr/local/bin that came from some
> experimental compilations of egcs. Because of my path, configure found
> and used this one ;-(

Auch.

That means a new gcc-compiled libc6 package won't have this
__register_frame_info function. That would break a large ammount of
packages. What's the best course of action now?

One idea:

* Compile libc6 2.0.7u-6 with gcc and put a (>= 2.0.7u-6) on the -dev
  package. 
* Make a tiny i386-only (other archs don't have this problem) library
  lib__register_frame_info.so.0 that provides the missing function (where do
  we obtain this function from? The egcs source?); preload this.
* Before releasing slink, make sure nothing has a Dependency like libc6 (>=
  2.0.7u-4) or libc6 (>= 2.0.7u-5). File a massive critical bug report
  against this packages -- if the maintainer can confirm the package doesn't
  suffer from this (objdump is your friend here), close the bug.
* When all this bugs have been closed, release a new libc6 with this extra
  library removed (we don't want to carry this forever, do we?)

The last point is the most problematic one, because there's no way to assure
noone will upgrade the libc6 package leaving an old package installed. The
third point could be automated unpacking the packages on master and avoid
the nasty unnecessary bug reports.

Am I nuts?


							Marcelo


Reply to: