From owner-freebsd-java@FreeBSD.ORG Fri Apr 7 13:53:58 2006 Return-Path: X-Original-To: freebsd-java@freebsd.org Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E1DE16A400; Fri, 7 Apr 2006 13:53:58 +0000 (UTC) (envelope-from kurt@intricatesoftware.com) Received: from mta4.srv.hcvlny.cv.net (mta4.srv.hcvlny.cv.net [167.206.4.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id E65B843D45; Fri, 7 Apr 2006 13:53:57 +0000 (GMT) (envelope-from kurt@intricatesoftware.com) Received: from [172.16.1.72] (ool-457a77e8.dyn.optonline.net [69.122.119.232]) by mta4.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0IXC009QUUL2VR6T@mta4.srv.hcvlny.cv.net>; Fri, 07 Apr 2006 09:53:28 -0400 (EDT) Date: Fri, 07 Apr 2006 09:48:10 -0400 From: Kurt Miller In-reply-to: To: Daniel Eischen , freebsd-java@freebsd.org Message-id: <200604070948.11120.kurt@intricatesoftware.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline References: User-Agent: KMail/1.9.1 Cc: Subject: Re: Diablo 1.5 SIGBUS X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 13:53:58 -0000 On Thursday 06 April 2006 11:41 pm, Daniel Eischen wrote: > On Thu, 6 Apr 2006, Kurt Miller wrote: > > > On Thursday 06 April 2006 8:49 pm, odela01 wrote: > > > I applied the patch and did "make all install" in /usr/src/lib/libpthread, > > > but it didn't make any difference. I'll try to arrange access to the core > > > dump. > > > > > > > Thanks for making the core dump available to me. It was > > helpful. I got a partial stack trace from it: > > > > #0 0x280aa41b in pthread_setcancelstate () from /usr/lib/libpthread.so.2 > > #1 0x280a29a6 in pthread_mutexattr_init () from /usr/lib/libpthread.so.2 > > #2 0x00000000 in ?? () > > > > This bt also supports Dan Nelson's observations that this > > could be a threading issue. It would be great if you or Dan > > built a debug pthreads by commenting the CFLAGS+= -g line in > > /usr/src/lib/pthreads/Makefile and rebuilding/reinstall > > pthreads. The back-trace from the core file would contain > > line numbers and be more useful then. > > That stack trace doesn't help. pthread_mutexattr_init(), doesn't > call pthread_setcancelstate(). > > Is there any fork()ing going on? > Hi Daniel, One of the reports indicated RabbIT3 (http://www.khelekore.org/rabbit/) was causing failures. It doesn't do any fork()ing. -Kurt