From owner-freebsd-current Sun Jun 30 23:40:46 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 72E3F37B406 for ; Sun, 30 Jun 2002 23:40:26 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7996243E1A for ; Sun, 30 Jun 2002 23:40:25 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701064024.ZVGK6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 06:40:24 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA88923; Sun, 30 Jun 2002 23:27:09 -0700 (PDT) Date: Sun, 30 Jun 2002 23:27:08 -0700 (PDT) From: Julian Elischer To: Wesley Morgan Cc: Bill Huey , Michael Nottebrock , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: <20020701015122.I11313-100000@volatile.chemikals.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 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? We need to eliminate one of these two changes... I think it's likely that it's breakage in signals from KSE but I'd like to know that before I tear even more hair out chasing this.. SO, I'm suffering from brain fade now.. but please, signals is known to be in dire need of cleanup after the KSE edit, (signals are delivered to processes but can effect individual threads. yuck) Anyone who can help identify the problem please do.. I'm off to bed before my head explodes.. I'll be back tomorrow AM. I'm going to spend as much of msuspension sleeping as possible :-) On Mon, 1 Jul 2002, Wesley Morgan wrote: > I see this problem too. Luckily I have my entire KDE and QT system build > with debugging symbols... However, the problem is definitely in the > libc_r... I get virtually the same dump as Michael. > > #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > #1 0x28e8c9a7 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > #2 0xd0d0d0d0 in ?? () > #3 0x00000001 in ?? () > #4 0x00005f28 in ?? () > > > > On Sun, 30 Jun 2002, Bill Huey wrote: > > > On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: > > > Program received signal SIGSEGV, Segmentation fault. > > > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > > (gdb) bt > > > #0 0x281cc918 in _thread_kern_sched_state_unlock () from > > > /usr/lib/libc_r.so.5 > > > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > > > #2 0xd0d0d0d0 in ?? () > > > #3 0x080570b0 in ?? () > > > > This is unlikely to be a KSE problem. > > > > What do the rest of the threads look like ? > > > > Try "info threads" in gdb and then progressively walking through the thread > > list with "thread N", N being the thread number. I ran into a funny > > create at thread start up time crash and I'm wondering if it could > > be the same thing. > > > > bill > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > _ __ ___ ____ ___ ___ ___ > Wesley N Morgan _ __ ___ | _ ) __| \ > morganw@chemikals.org _ __ | _ \._ \ |) | > FreeBSD: The Power To Serve _ |___/___/___/ > Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! > > > 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