Results 1 to 3 of 3
  1. #1
    narfman0 is offline Member
    Join Date
    Nov 2009
    Posts
    3
    Rep Power
    0

    Default Eclipse 3.4.2/3.5.* GUI debug unresponsive system error

    Hello all,

    I have an issue when I hit a breakpoint in eclipse - everything (system included, not just java ui components) is unresponsive. It is not all breakpoints, but many having to do with the UI. (Don't know if it's related.) The problem is when I hit the breakpoint, my system seems unresponsive. The mouse moves smoothly, but no keyboard input breaks out of the system frozen state, and mouse clicks/scroll wheel do nothing. I have conky running in the background and it is updating fine, but nothing is suspicious there. I have to eventually hard power off my computer. Now I've experienced it on multiple machines and am concerned - fedora 10/11, eclipse 3.4.2 and 3.5.*, jdk1.6.0_14 and jdk1.6.0_16. A couple of unique things- on startup I pass -Xmx512m -Xms128m. I can't get super specific (it doesn't seem like a code specific problem, rather environment) but there's some information, if anyone recognizes the error.

    To reproduce, I start my debug configuration and activate some UI element where one of several breakpoints is activated.

    Has anyone experienced this or know the problem?

  2. #2
    narfman0 is offline Member
    Join Date
    Nov 2009
    Posts
    3
    Rep Power
    0

    Default A little more info

    The eclipse console itself is still displaying system.out.printlns from other threads. The processor is not at 100%, it's at normal operating level. It's as if input were hijacked. Also, centos 5.4 tested with jdk1.6.0_16.

    I can Ctrl-Alt-F2 and killall java, and when I go back, all is well again.

    I'd still like to debug my app!
    Last edited by narfman0; 11-04-2009 at 10:40 PM.

  3. #3
    narfman0 is offline Member
    Join Date
    Nov 2009
    Posts
    3
    Rep Power
    0

    Default

    Found out why we freeze in debug mode, it appears to be a problem with java itself not handling window grabs correctly.

    To fix this problem in fedora 10, we first must allow the x server to deactivate window grabs.
    vim /etc/X11/xorg.conf
    locate the section "ServerFlags," and in there add a line saying:
    Option "AllowDeactivateGrabs" "yes"
    now restart the x server (Ctrl-Alt-Backspace).
    This option enables the use of the Ctrl+Alt+Keypad-Divide key sequence to deactivate any active keyboard and mouse grabs.

    References:
    wiki.netbeans.org/FaqDebuggingAWTXWindows
    bugs.sun.com/bugdatabase/view_bug.do?bug_id=6517045
    man xorg.conf

Similar Threads

  1. GWT Eclipse 3.5 Plugin Debug Problems
    By jwolfrum in forum Eclipse
    Replies: 2
    Last Post: 06-14-2010, 10:20 AM
  2. error debug
    By stid in forum Eclipse
    Replies: 2
    Last Post: 10-16-2009, 07:44 PM
  3. Eclipse debug when ant uses temp files
    By aiancu in forum Eclipse
    Replies: 0
    Last Post: 04-21-2009, 03:58 PM
  4. How to enable debug mode in eclipse
    By msgbharath in forum New To Java
    Replies: 3
    Last Post: 01-10-2009, 02:20 AM
  5. Cannot debug on Eclipse.. and other IDE
    By pexlee in forum Eclipse
    Replies: 0
    Last Post: 09-26-2008, 05:07 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •