From owner-freebsd-current Mon Jul 1 0:14:25 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 8CA7437B400 for ; Mon, 1 Jul 2002 00:14:23 -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 08DDC43E0A for ; Mon, 1 Jul 2002 00:14:23 -0700 (PDT) (envelope-from billh@gnuppy.monkey.org) Received: from billh by gnuppy.monkey.org with local (Exim 3.35 #1 (Debian)) id 17OvO5-0000ai-00; Mon, 01 Jul 2002 00:14:17 -0700 Date: Mon, 1 Jul 2002 00:14:17 -0700 To: Wesley Morgan Cc: Julian Elischer , Michael Nottebrock , freebsd-current@FreeBSD.ORG, Bill Huey Subject: Re: Post-KSE disaster with libc_r Message-ID: <20020701071417.GA2208@gnuppy.monkey.org> References: <20020701024638.X11550-100000@volatile.chemikals.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020701024638.X11550-100000@volatile.chemikals.org> 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 02:59:09AM -0400, Wesley Morgan wrote: > 2723 kdeinit CALL gettimeofday(0x28e94ab8,0) > 2723 kdeinit RET gettimeofday 0 > 2723 kdeinit CALL wait4(0xffffffff,0,0x1,0) > 2723 kdeinit RET wait4 2724/0xaa4 > 2723 kdeinit CALL poll(0x8059000,0x1,0) > 2723 kdeinit RET poll 1 > 2723 kdeinit PSIG SIGSEGV SIG_DFL > 2723 kdeinit NAMI "kdeinit.core" > > Both the kdeinit and a child it forks are dying... Setting a breakpoint of > fork() in the binary shows: That's almost definitely the same problem I'm running into with the JVM, however it registered itself has an infinite hang since SEGV deliveries are turned off when inside in a crashing/SEGVing libc_r thread-kernel. bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message