From owner-freebsd-java@FreeBSD.ORG Wed Apr 9 13:20:02 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 5164637B401 for ; Wed, 9 Apr 2003 13:20:02 -0700 (PDT) Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE9C143F75 for ; Wed, 9 Apr 2003 13:20:01 -0700 (PDT) (envelope-from jj@alicia.nttmcl.com) Received: from alicia.nttmcl.com (localhost [127.0.0.1]) by alicia.nttmcl.com (8.12.5/8.12.5) with ESMTP id h39KK1vm030271; Wed, 9 Apr 2003 13:20:01 -0700 (PDT) (envelope-from jj@alicia.nttmcl.com) Received: (from jj@localhost) by alicia.nttmcl.com (8.12.5/8.12.5/Submit) id h39KK1p4030270; Wed, 9 Apr 2003 13:20:01 -0700 (PDT) Date: Wed, 9 Apr 2003 13:20:01 -0700 From: Shannon -jj Behrens To: FT Message-ID: <20030409202001.GA30227@alicia.nttmcl.com> References: <3518113640.20030409174915@kengu.ru> <200304091612.24472.ernst.dehaan@nl.wanadoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304091612.24472.ernst.dehaan@nl.wanadoo.com> User-Agent: Mutt/1.4i cc: Ernst de Haan 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: Wed, 09 Apr 2003 20:20:02 -0000 Aren't signal 11's usually the result of bad memory (e.g. bad memory)? Best Regards, -jj On Wed, Apr 09, 2003 at 03:12:24PM +0100, Ernst de Haan wrote: > Wasn't this due to some kernel option or so? I don't remember the exact > details though. Search the archives. > > Ernst > > > On Wednesday 09 April 2003 15:49, FT wrote: > > Hello, > > > > I've installed compat3x-i386-4.4.20020925 and JDK 1.1.8 from ports on > > FreeBSD 4.7 stable. > > And now I have problem: when I try to execute, for example, javac, I > > get following message: > > > > SIGSEGV 11* segmentation violation > > > > Full thread dump: > > Monitor Cache Dump: > > Registered Monitor Dump: > > Monitor IO lock: <unowned> > > Child death monitor: <unowned> > > Event monitor: <unowned> > > I/O monitor: <unowned> > > Alarm monitor: <unowned> > > Memory allocation lock: <unowned> > > Monitor registry: <unowned> > > Thread Alarm Q: > > Abort trap > > > > I know that I'm not first who confront with this problem, but I can't > > find how to solve it. -- Hacker is to software engineer as Climbing Mt. Everest is to building a Denny's there.