From owner-freebsd-java@FreeBSD.ORG Fri Dec 19 06:12:39 2003 Return-Path: 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 D6D2D16A4CE for ; Fri, 19 Dec 2003 06:12:39 -0800 (PST) Received: from turing.morons.org (turing.morons.org [209.237.229.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBCE443D46 for ; Fri, 19 Dec 2003 06:12:38 -0800 (PST) (envelope-from freebsd@spatula.net) Received: by turing.morons.org (Postfix, from userid 1001) id CB635A927; Fri, 19 Dec 2003 06:12:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by turing.morons.org (Postfix) with ESMTP id C8E53A920; Fri, 19 Dec 2003 06:12:38 -0800 (PST) Date: Fri, 19 Dec 2003 06:12:38 -0800 (PST) From: Nick Johnson X-X-Sender: spatula@turing.morons.org To: Sebastiaan van Erk In-Reply-To: <1071830891.66714.3.camel@blauwoor.sebster.com> Message-ID: <20031219061001.C30962@turing.morons.org> References: <1071830891.66714.3.camel@blauwoor.sebster.com> X-what-happen: someone set up us the bomb X-Message-Flags: Spatula Precedence: special-delivery MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-java@freebsd.org Subject: Re: bug report jdk1.4.2 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2003 14:12:39 -0000 I think this might be the same thing as my open bug: http://www.freebsd.org/cgi/query-pr.cgi?pr=60083 Can you get a java.core file and do this with it: gdb java_g java.core And when gdb starts up, do a "bt" and see if your stack trace includes something like this: #11 0x280cd782 in getservent () from /usr/lib/libc_r.so.4 #12 0x280ccc3d in getservbyname () from /usr/lib/libc_r.so.4 #13 0x280cb48c in getaddrinfo () from /usr/lib/libc_r.so.4 Nick On Fri, 19 Dec 2003, Sebastiaan van Erk wrote: > Hi all, > > I'm running FreeBSD 4.9-RELEASE with native JDK 1.4.2, and I get the > following VM crash (see below). It's consistent, I.E. it crashes EVERY > time. Does anybody know a work around? > -- "The aptly-named morons.org is an obscenity-laced screed..." -- Robert P. Lockwood, Catholic League director of research Nick Johnson, version 2.1 http://web.morons.org/