Brad Giaccio [[EMAIL PROTECTED]] wrote:

>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.

I would like to suggest a technique that may be too difficult if you
applet is large,
but may work for you.  Before each wait, print 'thread_name: waiting on
object xxx'
and after the wait print 'thread_name: wait stopped'.  You should then
see a
'waiting on object xxx' message without a corresponding 'wait stopped'
when
you deadlock.  Hope this helps.

        Paul Gassoway

Reply via email to