<flame inspiring text>
Of all the debuggers I've come across for Java (most suck unmentionable
things), Sun's JavaWorkshop seems to be the best. It's written in Java,
so expect it to crash a fair amount; but it allows you to get waist deep
into the various stack frames of all your threads, inside a nice gui.
Problem? Sun puts it out for Windows and Solaris. I've heard mention
that it works under Linux with a patch from "SuSE", but that some features
don't work in such operation. As I do development on NT/Linux at work, I
use it on NT.
There's a trial version to be had (JWS):
http://shop.sun.com/cgi-bin/statetrack/parts/796-0044-01/index.html?*:19980716004945~17703&*:1
</flame inspiring text>
On Wed, 15 Jul 1998, Brad Giaccio wrote:
> Date: Wed, 15 Jul 1998 13:44:31 -0400 (EDT)
> From: Brad Giaccio <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: debugging an applet
> Resent-Date: Wed, 15 Jul 1998 13:43:44 -0400
> Resent-From: [EMAIL PROTECTED]
>
> well I've seen a number of you mention debuggers for java apps but I seem
> to be going in to deadlock somewhere in my applet and have already spent
> three days searching I 've. Does anyone one have a good debugger for
> applets it doesn't need to be robust basically what I need is to run the
> applet in a debugger, then lock it up and have the debugger tell me where
> all the threads are so I can find my deadlock.
>
> Yes I've tried
> jdb and jikes with sun.applet.AppletViewer <page> but when I do this
> appletviewer dumps core on the first line of my init which is super().
> But by itself it doesn't dump core.
>
> Hope someone can help,
>
> Thanks,
> Brad
>
> --
> --- There are two kinds of knowledge, you either know the answer or
> you know where to find it
> -Kane, Johnson, and anonymous
>
_____________________________________________________________________________
"The human mind is a 400,000-year-old legacy application...and you expected
to find structured programming?" -- Randall Davis, 1996 AAAI Pres. Address
