On Tue, 2005-05-17 at 09:51 -0600, Tom Tromey wrote: > Could you use gdb and see how it is deadlocking? What it is waiting > for? I tried that earlier, and one of the thread stack traces was completely botched. I think it must have been the AWT event thread (that's a separate thread, right?). AG