Date: Sun, 30 Jun 2002 22:30:56 -0700 From: Bill Huey <billh@gnuppy.monkey.org> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: freebsd-current@freebsd.org, Bill Huey <billh@gnuppy.monkey.org> Subject: Re: Post-KSE desaster Message-ID: <20020701053056.GA1907@gnuppy.monkey.org> In-Reply-To: <3D1FE483.4010002@gmx.net> References: <3D1FE483.4010002@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020701053056.GA1907>