From owner-freebsd-java@FreeBSD.ORG Wed Apr 9 20:56:48 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 05EAE37B401 for ; Wed, 9 Apr 2003 20:56:48 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B7F143FD7 for ; Wed, 9 Apr 2003 20:56:46 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 193Rby-0003nu-00; Wed, 9 Apr 2003 19:16:22 -0700 Date: Wed, 9 Apr 2003 19:16:18 -0700 (PDT) From: Tom Samplonius To: Shannon -jj Behrens In-Reply-To: <20030409202001.GA30227@alicia.nttmcl.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Ernst de Haan cc: FT cc: freebsd-java@freebsd.org Subject: Re: Java 1.1.8 sigserv 11 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 03:56:48 -0000 On Wed, 9 Apr 2003, Shannon -jj Behrens wrote: > Aren't signal 11's usually the result of bad memory (e.g. bad memory)? > > Best Regards, > -jj Possibly, but they are also the result of a process accessing memory it should not (eg. program error). With bad hardware, signal 11s occur, because pointers get corrupted by the hardware, resulting in the program accidently accessing memory it should not. In this case, jdk1.1.8 is such an old build, that it probably a library incompatiblity problem between FreeBSD 3 and 4. Compatibility libraries are available, but I don't know how well they are tested. And the underlying kernel has changed significantly too. It would probably work if it was rebuilt on a FreeBSD 4.x system. Tom