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

Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore



On Tue, 7 Jun 2011, Jonathan Nieder wrote:

> Sven-Haegar Koch wrote:
> 
> > While upgrading from libc6 2.13-4 to 2.13-5 on a i386 system:
> >
> > Preparing to replace libc6 2.13-4 (using .../archives/libc6_2.13-5_i386.deb) ...
> > Unpacking replacement libc6 ...
> > Setting up libc6 (2.13-5) ...
> > Installing new version of config file /etc/ld.so.conf.d/i486-linux-gnu.conf ...
> > Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! "bad dynamic tag"' failed!
> 
> Very odd.  That assertion doesn't exist in current glibc; in fact,
> it was was removed in glibc 2.3!  (cvs/glibc-2-3~925,
> elf/dynamic-link.h (elf_get_dynamic_info): Don't abort on unknown
> dynamic tags, 2002-04-03).
> 
> But it was in an inline function in that header, so if some binary
> package was built on a machine with ancient libc6-dev, that could be a
> half-explanation.  Where do you get your binary packages from?

ftp.de.debian.org

But the system has been updated on Debian Unstable since Debian Woody 
(and moved from PC to PC, from harddisk to harddisk, without reinstall).

I see the following strange thing on my system:

haegar@aurora:/lib$ ls -l ld*
-rwxr-xr-x 1 root root 117960 2011-05-12 11:21 ld-2.13.so
-rwxr-xr-x 1 root root  90210 2002-09-18 11:40 ld-2.2.5.so
lrwxrwxrwx 1 root root     10 2011-05-12 11:21 ld-linux.so.2 -> ld-2.13.so
-rwxr-xr-x 1 root root  99568 2001-03-07 03:17 ld.so

haegar@aurora:/lib$ dpkg -S /lib/ld.so
dpkg-query: no path found matching pattern /lib/ld.so.
haegar@aurora:/lib$ dpkg -S /lib/ld-2.2.5.so 
dpkg-query: no path found matching pattern /lib/ld-2.2.5.so.

Could it be that some old glibc did not remove the files on upgrade, and 
they have been there forever, and unknowingly been used even with way 
newer libc6 installed?

c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.



Reply to: