From owner-freebsd-current Mon Jul 1 12: 9:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F5D37B400 for ; Mon, 1 Jul 2002 12:09:45 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02DDA43E35 for ; Mon, 1 Jul 2002 12:02:00 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (localhost [127.0.0.1]) by nagual.pp.ru (8.12.4/8.12.3) with ESMTP id g61IbKTa003574; Mon, 1 Jul 2002 22:47:27 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.4/8.12.3/Submit) id g61IXDk5003541; Mon, 1 Jul 2002 22:33:20 +0400 (MSD) (envelope-from ache) Date: Mon, 1 Jul 2002 22:32:48 +0400 From: "Andrey A. Chernov" To: Julian Elischer Cc: NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r Message-ID: <20020701183102.GA2833@nagual.pp.ru> References: <87bs9rzpa8.fsf@boggy.acest.tutrp.tut.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 01, 2002 at 10:26:22 -0700, Julian Elischer wrote: > the question is: > did you update both kernel and userland? This bug is not related to in-kernel KSE code (but, maybe related to header files compiled in). I got it even with updated userland and old pre-KSE kernel (with both updated I have it too). Only switching to libc_r old about month ago helps. > > > On Mon, 1 Jul 2002, NAKAJI Hiroyuki wrote: > > > >>>>> In <1025516273.442.5.camel@leeloo.intern.geht.de> > > >>>>> Marc Recht wrote: > > > > > Can someone please check out a libc_r tree as of 3 days ago > > > and try that... > > > > > > There was a commit in libc_r/uthreads 2 days ago that might be relevant. > > > failing that, can someone try newly compiled utilities on an older pre-KSE > > > kernel? > > > > MR> I don't know if this helps, but I've a pre-KSE userland (28.06.), a > > MR> post-KSE kernel (30.06.) and I've none of the described problems. > > MR> Evolution, KDE3, Mozilla, ogg123, jdk13 all run without a problem. > > > > I updated my current box about an hour ago, and got into trouble too. > > > > My case is that amavis-milter dumps core with signal 11 and I cannot check > > virus in emails. :( > > > > $ sudo gdb ./amavis-milter /etc/mail/amavis-milter.core > > GNU gdb 5.2.0 (FreeBSD) 20020627 > > Copyright 2002 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "i386-undermydesk-freebsd"... > > Core was generated by `amavis-milter'. > > Program terminated with signal 11, Segmentation fault. > > Reading symbols from /usr/lib/libmilter.so.2...done. > > Loaded symbols for /usr/lib/libmilter.so.2 > > Reading symbols from /usr/lib/libc_r.so.5...done. > > Loaded symbols for /usr/lib/libc_r.so.5 > > Reading symbols from /usr/lib/libc.so.5...done. > > Loaded symbols for /usr/lib/libc.so.5 > > Reading symbols from /usr/libexec/ld-elf.so.1...done. > > Loaded symbols for /usr/libexec/ld-elf.so.1 > > #0 0x2808e918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > (gdb) > > -- > > NAKAJI Hiroyuki > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message