------- Comment #9 from hendrich at informatik dot uni-hamburg dot de 2006-06-08 12:25 ------- (In reply to comment #8) > This seems to be a deadlock happening when the HideCursorManager sets the > cursor at some inconvenient time. I haven't debugged it fully yet.
Good catch! This sounds very possible. When I tried gdb on this, I just got lots of waiting threads, but didn't notice any of the cursor hiding stuff. > It probably > deserves its own bug report. Is there an easy way to disable the > HideCursorManager? Not yet... (it is probably easiest to uncomment all setCursor calls in Niffler.java). I hope that get/setCursor is considered a thread-safe AWT operation. Using SwingUtilities.invokeLater would probably not help, or would it? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27917 _______________________________________________ Bug-classpath mailing list Bug-classpath@gnu.org http://lists.gnu.org/mailman/listinfo/bug-classpath
