Mo,
I did as you suggested (this is the first time I've run jdb, so I hope I am
using it to best advantage).
I have 7 Threads:
Thread-1 (running)
AWT-EventQueue-0 (cond. wait)
PostEventQueue-0 (cond. wait)
AWT-Windows (running)
IFC (cond. wait) (Yes, I am using IFC!)
Time
Run this same code in Jacl under jdb. When it locks up, interupt
the code and see which threads are locked. You should then be able
to get a backtrace for each of the threads to find out where
the deadlock is. I think this bug in in the notifier somewhere, so
it should deadlock both Jacl and Tcl B
I am making a lot of progress today understanding the JavaBean event
processing. But I am now stuck again.
In the class EventAdaptor.java the method _processEvent(...) has the
following code:
BeanEvent evt = new BeanEvent( interp, paramTypes, params, cmd );
interp.getNotifier().queueEvent( ev
