From owner-freebsd-hackers Sun Oct 6 15:12:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15059 for hackers-outgoing; Sun, 6 Oct 1996 15:12:49 -0700 (PDT) Received: from covina.lightside.com (covina.lightside.com [207.67.176.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA15051 for ; Sun, 6 Oct 1996 15:12:44 -0700 (PDT) Received: from localhost (jehamby@localhost) by covina.lightside.com (8.8.0/8.7.3) with SMTP id PAA11824; Sun, 6 Oct 1996 15:11:55 -0700 (PDT) Date: Sun, 6 Oct 1996 15:11:52 -0700 (PDT) From: Jake Hamby To: Mark Mayo cc: hackers@freebsd.org Subject: Re: JDK 1.0.2 SIGSEGV?! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Oct 1996, Mark Mayo wrote: > On Sat, 5 Oct 1996, Jake Hamby wrote: > > > Has anyone tried the FreeBSD JDK 1.0.2 that was recently posted? For some > > reason, it always crashes with a SIGSEGV, and prints: > > > > SIGSEGV 11* segmentation violation > > sig 11, code 12 or 0xc, sc 0xefbfd710, addr 0x1c > > > > Full thread dump: > > > > ... and then it hangs here ... > > What is crashing? javac, java, or appletviewer?? On my system, everything > run just fine!! The only exception was the appletviewer, which crashed out > just like you mentioned unless it was running in 8bpp or 24bpp -- so when > I ran appletviewer on 32k colors, it dumped out.. I'm assuming this is > your problem. Also, I had to change the scripts a little to hardwire in > my CLASSPATH and substituted `arch` with i386. > > Otherwise, the JDK works great (I've been using it all weekend for a > course!) -- many thanks to the author! I would be col, however, if the > appletviewer would work in 16bpp --> then FreeBSD would be better than Sun > for java developemnt :-) > > cya, > -Mark All three programs are crashing, because all three point to the same program! (javac and appletviewer are shell scripts). I'm running in 8bpp color, also. I suspect this is a change that has been made recently to FreeBSD-current, otherwise I don't know how to explain it. Anyone else? -- Jake