Why when starting GWT in debug mode, my break points don't break

Question

I am using Eclipse 3.4.2 with the latest GWT. The IDE doesn't even switch to Debug Perspective automatically.

Answer 1

I have found a different thread in groups discussing my problem.

http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/a9b553a6df5da5b8/65298c48c32deac0?lnk=raot&pli=1

Basically, JDK 1.6.0_14 will not work with GWT in eclipse debug mode. Switching a different JDK will work.

Answer 2

I want to confirm that Basically, JDK 1.6.0_14 will not work with GWT in eclipse debug mode. Switching a different JDK will work.

I installed JDK 1.6.0_13 and the eclipse debug perspective kicked in. Using eclipse 3.3.2

Thanks for the tip!

Answer 3

I'm running 1.6.0_13 and still the debug doesn't work. It just doesn't hit the breakpoints. And more, the page shows up blank in hosted mode (except for the static content in the HTML file), but everything displays and works correctly when running on the browser.

java -version
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)

Answer 4

Also confirming that the debugger does not work with 1.6.0_14. A downgrade to 1.6.0_13 solved my issue. Farinha, might you still have your java_home (or something similar) pointing to an install of 1.6.0_14 even though you have installed 1.6.0_13?

Answer 5

Upgraded to jdk1.6.0_17 - Works fine

Answer 6

Changing the JDK didn't help in my case, but I have finally found out what's wrong.

When moving from GWT 1.7 to 2.0 the old GWT classes will stay on the war ouput. They must be manually deleted in order for 2.0 to kick in.

Answer 7

I had the same problem. In my case the problem was that I was using JRE instead of JDK. Setting JDK instead of JRE, solved my problem. I recommend reviewing the build configuration to see which one is being used.