From owner-freebsd-java@FreeBSD.ORG Mon Sep 4 04:34:30 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 B75E216A4DA for ; Mon, 4 Sep 2006 04:34:30 +0000 (UTC) (envelope-from davidn@datalinktech.com.au) Received: from mail-ihug.icp-qv1-irony2.iinet.net.au (ihug-mail.icp-qv1-irony2.iinet.net.au [203.59.1.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07C8A43D46 for ; Mon, 4 Sep 2006 04:34:29 +0000 (GMT) (envelope-from davidn@datalinktech.com.au) Received: from 203-206-162-119.perm.iinet.net.au (HELO mail.datalinktech.com.au) ([203.206.162.119]) by mail-ihug.icp-qv1-irony2.iinet.net.au with ESMTP; 04 Sep 2006 12:34:26 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.08,205,1154880000"; d="scan'208"; a="617007249:sNHT1617094044" Received: from [192.168.4.232] (AtomAnt.datalink.loc [192.168.4.232]) by mail.datalinktech.com.au with esmtp; Mon, 04 Sep 2006 14:34:26 +1000 id 0017B842.44FBACD2.00008CF5 Message-ID: <44FBACB6.1030604@datalinktech.com.au> Date: Mon, 04 Sep 2006 14:33:58 +1000 From: David Nugent User-Agent: Thunderbird 1.5.0.4 (X11/20060704) MIME-Version: 1.0 To: Yamada Ken Takeshi References: <20060901.230842.74753654.ken@tydfam.jp> In-Reply-To: <20060901.230842.74753654.ken@tydfam.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-java@freebsd.org Subject: Re: diablo-jdk1.5.0 core dumps w/ -current 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: Mon, 04 Sep 2006 04:34:30 -0000 Yamada Ken Takeshi wrote: > Recent -current, ca. a week or so causes a crash like below. > Is it unique to me? or commonly noticed? > Noticed first a few weeks ago in -current. You would need to rebuild jdk against recent -current libc and threading libraries to return functionality due to -current's thread libraries (which have had no version bump yet) being dependent on functionality in -current's libc.7, but diablo loads libc.6. As a fast workaround if you just want to get diablo working again, you should be able to libmap.conf one of the other thread libs instead of libthr. I don't know how well it works, but others have reported success.