Bug#547059: marked as done (ldd hosed)
Your message dated Thu, 17 Sep 2009 15:25:53 +0200
with message-id <20090917132553.GA12388@bogon.sigxcpu.org>
and subject line Re: Bug#547059: ldd hosed
has caused the Debian Bug report #547059,
regarding ldd hosed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
547059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547059
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libc-bin
Version: 2.9-26
Severity: normal
ldd is unusable here:
$ ldd -v /bin/ls
But this seems to be the root cause:
$ /lib/ld-linux.so.2 --verify /bin/ls
Illegal instruction (core dumped)
Cheers,
-- Guido
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.31-rc6 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Sep 17, 2009 at 01:28:42PM +0200, Aurelien Jarno wrote:
> tag 547059 + unreproducible + moreinfo
> thanks
>
> Guido Günther a écrit :
> > Package: libc-bin
> > Version: 2.9-26
> > Severity: normal
> >
> > ldd is unusable here:
> >
> > $ ldd -v /bin/ls
> >
> > But this seems to be the root cause:
> >
> > $ /lib/ld-linux.so.2 --verify /bin/ls
> > Illegal instruction (core dumped)
> >
>
> That's not reproducible here. Could you verify the checksum of
> /lib/ld-2.9.so and check with another (non -rc) kernel?
Hmm...reinstalling the packaged indeed changed the md5sum and it works
now. Now idea how this happened, I'll keep looking - for now the report
can be closed though.
-- Guido
--- End Message ---
Reply to: