Date: Fri, 26 Mar 2004 12:40:20 -0800 From: Sean McNeil <sean@mcneil.com> To: "Jacques A. Vidrine" <nectar@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: nss_ldap broken Message-ID: <1080333620.9866.4.camel@server.mcneil.com> In-Reply-To: <20040326125934.GA68357@madman.celabo.org> References: <1080273717.18231.10.camel@server.mcneil.com> <20040326125934.GA68357@madman.celabo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2004-03-26 at 04:59, Jacques A. Vidrine wrote:
> Hmm, it does seem that there is an error situation where that could
> be the case, but the problem description above doesn't follow from
> that case. The patch will fix it. (The situation would occur if
> /etc/nsswitch.conf existed, but was not readable.)
>
> > Does anyone have any insight into what this might be? I would love to
> > have it working again.
>
> I will try to reproduce here. So far no luck.
Interesting!!! Not what I had thought was going on. I compiled libc
with symbols and I get this:
#0 0x28214800 in ?? ()
#1 0x2816be35 in nss_atexit () at
/usr/src/lib/libc/net/nsdispatch.c:518
#2 0x2818e9db in __cxa_finalize (dso=0x0)
at /usr/src/lib/libc/stdlib/atexit.c:184
#3 0x2818e6fc in exit (status=672827136) at
/usr/src/lib/libc/stdlib/exit.c:69
#4 0x08049b68 in free () at /usr/src/lib/libc/stdlib/malloc.c:1153
#5 0x08049279 in free () at /usr/src/lib/libc/stdlib/malloc.c:1153
So even though the write lock didn't cause a crash the unlock did.
I didn't try your patch as it looked like the locks were being
appropriately handled. Here is the real odd part:
passwd: ldap files
group: ldap files
works (no seg 11)!!
passwd: files ldap
group: files ldap
fails (seg 11)!!
Cheers,
Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1080333620.9866.4.camel>