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

Bug#583858: libc6-i686: many programs segfaults, including ls, login and dpkg



On Mon, May 31, 2010 at 03:26:02PM +0200, Aurelien Jarno wrote:
> lukpank@o2.pl a écrit :
> > Aurelien Jarno <aurelien@aurel32.net> writes:
> > 
> >> On Mon, May 31, 2010 at 12:19:03PM +0200, Łukasz Pankowski wrote:
> >>> Aurelien Jarno <aurelien@aurel32.net> writes:
> >>>
> >>>> On Mon, May 31, 2010 at 11:44:49AM +0200, Łukasz Pankowski wrote:
> >>>>> Aurelien Jarno <aurelien@aurel32.net> writes:
> >>>>>
> >>>>>> Everything looks correct. Can you also please also send us the output of 
> >>>>>> ls -l /lib ?
> >>>>> I can still get the segfault with
> >>>>>
> >>>>> $ LD_LIBRARY_PATH=/lib/i686-out-of-the-way/cmov ls
> >>>>> Naruszenie ochrony pamięci
> >>>> And what happens with: 
> >>>> LD_LIBRARY_PATH=/lib/i686-out-of-the-way/cmov /lib/i686-out-of-the-way/cmov/lib/ld-2.11.1.so /bin/ls
> >>>> ?
> >>>>
> >>>> Also, what is the output of:
> >>>> LD_LIBRARY_PATH=/lib/i686-out-of-the-way/cmov /lib/i686-out-of-the-way/cmov/lib/ld-2.11.1.so --list /bin/ls
> >>>> ?
> >>> There is no file matching /lib/i686-out-of-the-way/cmov/lib/ld*
> >>>
> >> Oops, it should have been /lib/i686-out-of-the-way/cmov/ld-2.11.1.so
> >> instead.
> > 
> > $ LD_LIBRARY_PATH=/lib/i686-out-of-the-way/cmov /lib/i686-out-of-the-way/cmov/ld-2.11.1.so /bin/ls
> > Segmentation fault
> > $ LD_LIBRARY_PATH=/lib/i686-out-of-the-way/cmov /lib/i686-out-of-the-way/cmov/ld-2.11.1.so --list /bin/ls
> > 	linux-gate.so.1 =>  (0xb771a000)
> > 	libselinux.so.1 => /lib/libselinux.so.1 (0xb76ee000)
> > 	librt.so.1 => /lib/i686-out-of-the-way/cmov/librt.so.1 (0xb76e4000)
> > 	libacl.so.1 => /lib/libacl.so.1 (0xb76dd000)
> > 	libc.so.6 => /lib/i686-out-of-the-way/cmov/libc.so.6 (0xb7591000)
> > 	libdl.so.2 => /lib/i686-out-of-the-way/cmov/libdl.so.2 (0xb758d000)
> > 	/lib/ld-linux.so.2 => /lib/i686-out-of-the-way/cmov/ld-2.11.1.so (0xb771b000)
> > 	libpthread.so.0 => /lib/i686-out-of-the-way/cmov/libpthread.so.0 (0xb7574000)
> > 	libattr.so.1 => /lib/libattr.so.1 (0xb756e000)
> 
> Again, everything looks fine here, and I am not able to reproduce the
> problem. I guess we will have to wait for other users having the same issue.
> 

I have just seen that I forgo to ask you details about your CPU. What's
the output of cat /proc/cpuinfo ?

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net



Reply to: