From owner-freebsd-current Sun Jun 30 22:54: 9 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 5D86C37B400 for ; Sun, 30 Jun 2002 22:54:06 -0700 (PDT) Received: from volatile.chemikals.org (cae88-49-048.sc.rr.com [24.88.49.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF9F643E09 for ; Sun, 30 Jun 2002 22:54:05 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.12.3/8.12.3) with ESMTP id g615s47C011338; Mon, 1 Jul 2002 01:54:04 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Mon, 1 Jul 2002 01:54:03 -0400 (EDT) From: Wesley Morgan To: Bill Huey Cc: Michael Nottebrock , Subject: Re: Post-KSE desaster In-Reply-To: <20020701053056.GA1907@gnuppy.monkey.org> Message-ID: <20020701015122.I11313-100000@volatile.chemikals.org> 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 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