This is the mail archive of the
libc-alpha@cygnus.com
mailing list for the glibc project.
Re: glibc-2.0.95 causes ls -al & ps -aux to segfault.
- To: hjl@lucon.org (H.J. Lu)
- Subject: Re: glibc-2.0.95 causes ls -al & ps -aux to segfault.
- From: Byron Faber <bfaber@ipinc.net>
- Date: Mon, 03 Aug 1998 07:31:44 +0000
- cc: aj@arthur.rhein-neckar.de (Andreas Jaeger), bfaber@ipinc.net, libc-alpha@cygnus.com
Ok, My fault, at least in that it didn't pass make check:
=========================
Starting process a
Starting process b
gcc -nostdlib -nostartfiles -o ex2 -Wl,-dynamic-linker=/lib/ld-linux.so.2 -g
../csu/crt1.o ../csu/crti.o `gcc --print-file-name=crtbegin.o` ex2.o
libpthread.so -Wl,-rpath-link=..:../math:../elf:../nss:../nis:../db2:../rt:../
resolv:. ../libc.so.6 ../libc_nonshared.a -lgcc `gcc
--print-file-name=crtend.o` ../csu/crtn.o
../elf/ld-linux.so.2 --library-path ..:../math:../elf:../nss:../nis:../db2:../r
t:../resolv:. ./ex2 > ex2.out
make[1]: *** [ex2.out] Error 139
make[1]: Leaving directory `/usr2/src/gnu/glibc-2.0.95/linuxthreads'
make: *** [linuxthreads/tests] Error 2
=========================
It dies in the linuxthreads check. (wierd)
> > Was `make check' successful? Do you consider this as a compiler or a
> > glibc2 bug?
I think its a glibc2 bug, given that it fails if I use gcc 2.8.1.
> > Can I you localize the problem with gdb/strace?
I'll give this a shot.
> > Is this a problem of ls in general or of `ls -l'? In that case the
> > lookup of user/group from /etc/passwd might be somehow broken. What
> > does /etc/nsswitch.conf look like?
Its attached. [I haven't touched this, so unless glibc touches it
on install, its the standard redhat 5.0 file].
> How did you install glibc 2.0.95 on RedHat 5.1? It is kind of
> tricky. It took me a while to figure it out. Here is my
>
> # ls -l /lib
>
I was naive enough to get glibc-2.0.94 installed and working by doing
a 'make check;make install', and then recompiling a few binaries
that dropped dead because of the libg++ problems introduced by glibc 2.1.
I'll take a look at gdb and ls.
Thanks for your input,
Byron
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
# nisplus or nis+ Use NIS+ (NIS version 3)
# nis or yp Use NIS (NIS version 2), also called YP
# dns Use DNS (Domain Name Service)
# files Use the local files
# [NOTFOUND=return] Stop searching if not found so far
#
passwd: files nisplus nis
shadow: files nisplus nis
group: files nisplus nis
hosts: files nisplus nis dns
services: nisplus [NOTFOUND=return] files
networks: nisplus [NOTFOUND=return] files
protocols: nisplus [NOTFOUND=return] files
rpc: nisplus [NOTFOUND=return] files
ethers: nisplus [NOTFOUND=return] files
netmasks: nisplus [NOTFOUND=return] files
bootparams: nisplus [NOTFOUND=return] files
netgroup: nisplus
publickey: nisplus
automount: files nisplus
aliases: files nisplus