Bug#204711: Assorted libc6 problems

2003-08-14 Thread Ivo Timmermans
Package: libc6
Version: 2.3.2-2
Followup-For: Bug #204711

Hi,

I have the same problems Guus describes.  I'm also using NIS, but
my nsswitch.conf is the default version provided by libc6, I only
put +:: in /etc/passwd.

Also zsh4-static segfaults.  This is weird, a static executable
that segfaults with one version of libc, but not another (2.3.2-2
segfaults, 2.3.1-17 doesn't).  The only thing that this executable
loads dynamically are libc's NSS files:

open("/lib/libnss_compat.so.2", O_RDONLY) = 3
open("/lib/libnsl.so.1", O_RDONLY)  = 3

and so on.  The segfault happens a little while later:

open("/etc/nsswitch.conf", O_RDONLY)= 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=465, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x4000
read(3, "# /etc/nsswitch.conf\n#\n# Example configuration of GNU Name Service 
Switch functionality.\n# If you have the `glibc-doc\' and `info\' packages installed, 
try:\n# `info libc \"Name Service Switch\"\' for information about this 
file.\n\npasswd: compat\ngr"..., 4096) = 465
read(3, "", 4096)   = 0
close(3)= 0
munmap(0x4000, 4096)= 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

All this leads me to think that there *is* something broken with
this version of the package.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux scarlet 2.4.20-xfs-hfsplus #1 zo jun 15 11:15:31 CEST 2003 i686
Locale: LANG=nl_NL, LC_CTYPE=nl_NL

Versions of packages libc6 depends on:
ii  libdb1-compat 2.1.3-7The Berkeley database routines [gl

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_COLLATE = "C",
LANG = "nl_NL"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#204711: Assorted libc6 problems

2003-08-14 Thread GOTO Masanori
At Sun, 10 Aug 2003 13:11:44 +0200,
Ivo Timmermans wrote:
> I have the same problems Guus describes.  I'm also using NIS, but
> my nsswitch.conf is the default version provided by libc6, I only
> put +:: in /etc/passwd.

If you disable NIS, is your problem resolved?

> Also zsh4-static segfaults.  This is weird, a static executable
> that segfaults with one version of libc, but not another (2.3.2-2
> segfaults, 2.3.1-17 doesn't).  The only thing that this executable
> loads dynamically are libc's NSS files:
> 
> open("/lib/libnss_compat.so.2", O_RDONLY) = 3
> open("/lib/libnsl.so.1", O_RDONLY)  = 3
> 
> and so on.  The segfault happens a little while later:

This zsh-static is another problem, and we can't fix this problem.
During 2.3.2 - 2.3.3 development, upstream modified libnss_compat
behavior.  We need to ask zsh-static maintainer to update zsh-static
for 2.3.2-2.  The reason is libnss uses dlopen (dynamic loading), and
static binaries which is linked against old libc6 also uses the new
incompatible libnss.

Regards,
-- gotom


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#204711: Assorted libc6 problems

2003-08-14 Thread Ivo Timmermans
GOTO Masanori wrote:
> At Sun, 10 Aug 2003 13:11:44 +0200,
> Ivo Timmermans wrote:
> > I have the same problems Guus describes.  I'm also using NIS, but
> > my nsswitch.conf is the default version provided by libc6, I only
> > put +:: in /etc/passwd.
> 
> If you disable NIS, is your problem resolved?

Well, a user that is in /etc/passwd, and not pulled in via NIS, can
log in.  If I remove the +:: line, it's exactly the same (except
ssh will react differently, because the NIS user doesn't exist then).


Ivo

-- 
... a Perl module would prefer that you stayed out of its living room
because you weren't invited, not because it has a shotgun.
- Programming Perl, O'Reilly


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]