From owner-java@FreeBSD.ORG Sun Dec 7 15:49:36 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA04463 for java-outgoing; Sun, 7 Dec 1997 15:49:36 -0800 (PST) (envelope-from owner-java@FreeBSD.ORG) Received: from osprey.grizzly.com (med.sc.scruznet.com [165.227.115.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA04453 for ; Sun, 7 Dec 1997 15:49:20 -0800 (PST) (envelope-from markd@osprey.grizzly.com) Received: (from markd@localhost) by osprey.grizzly.com (8.8.5/8.7.3) id PAA13749; Sun, 7 Dec 1997 15:50:48 -0800 (PST) Date: Sun, 7 Dec 1997 15:50:48 -0800 (PST) Message-Id: <199712072350.PAA13749@osprey.grizzly.com> From: Mark Diekhans To: njs3@doc.ic.ac.uk CC: freebsd-java@FreeBSD.ORG In-reply-to: (njs3@doc.ic.ac.uk) Subject: Re: which JDK to use? References: Sender: owner-java@FreeBSD.ORG Precedence: bulk >From: njs3@doc.ic.ac.uk (Niall Smart) >I just gave up on solaris 2.6/Intel, its too damn slow, and i've been >having problems with my window manager's stability that I am hoping to >cure by moving to FreeBSD. (I even recompiled XFree86 on Solaris 2.6, >didn't help) Sun doesn't really seem to care about Solaris/Intel, and this is understandable, as they make their money on hardware. FreeBSD has been a wonderfully stable and powerful development environment. >Do you know of any good debuggers that I can use for Java under FreeBSD? System.out.println() :_) Seriously, it works pretty well. At least 60% of the bugs I have encountered can be figured out by looking at the exception stack. For the rest, I have found Java to have a rather fast compile-run cycle, as the classes tend to be small. Sticking in println's and reruning might be crude, but its been a lot faster then waiting on JDB. Designing some debugging tracing from the start is not a bad idea. Have fun, Mark