Date: Sun, 7 Dec 1997 15:50:48 -0800 (PST) From: Mark Diekhans <markd@Grizzly.COM> To: njs3@doc.ic.ac.uk Cc: freebsd-java@FreeBSD.ORG Subject: Re: which JDK to use? Message-ID: <199712072350.PAA13749@osprey.grizzly.com> In-Reply-To: <E0xepWr-0000Zh-00@ash3.doc.ic.ac.uk> (njs3@doc.ic.ac.uk) References: <E0xepWr-0000Zh-00@ash3.doc.ic.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712072350.PAA13749>