From owner-freebsd-current Sun Jun 30 22:31: 4 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 8F10137B400 for ; Sun, 30 Jun 2002 22:30:59 -0700 (PDT) Received: from gnuppy.monkey.org (wsip68-15-8-100.sd.sd.cox.net [68.15.8.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A9EC43E13 for ; Sun, 30 Jun 2002 22:30:59 -0700 (PDT) (envelope-from billh@gnuppy.monkey.org) Received: from billh by gnuppy.monkey.org with local (Exim 3.35 #1 (Debian)) id 17Otm4-0000V5-00; Sun, 30 Jun 2002 22:30:56 -0700 Date: Sun, 30 Jun 2002 22:30:56 -0700 To: Michael Nottebrock Cc: freebsd-current@freebsd.org, Bill Huey Subject: Re: Post-KSE desaster Message-ID: <20020701053056.GA1907@gnuppy.monkey.org> References: <3D1FE483.4010002@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D1FE483.4010002@gmx.net> User-Agent: Mutt/1.4i From: Bill Huey 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 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