I have a SWT application that I am debugging using remote debugging in eclipse. If I set a breakpoint inside the SWT application event handler, my desktop with holes freezes. I can still switch to a text console by Strg+ Alt+ Fx. If I kill the SWT application from the console, everything will work.
Since this only happens when the breakpoint is inside the event handler, I highly suspect that the SWT blocks the event loop, causing everything to freeze. I guess there is some magic setting for SWT to βseparateβ applications, so I can debug correctly, but I cannot find it.
This is a known issue with custom widgets that have the capture of an X-pointer and not releasing it. The most common solution is to launch your internal eclipse on another display. I use Xvnc because I run into this problem all the time, but other examples are XNest .
I saw people trying to use -Dsun.awt.disablegrab=true. I don't know if this works or not.
-Dsun.awt.disablegrab=true
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=20006 for a long discussion of the problem and what people have tried.
Pw
Linux mint 11 JRE 1.6.0.xx, Swing . x11, , , , java.
-Dsun.awt.disablegrab=true .
VM , , , VM (, , ), IDE Eclipse .