Why are my breakpoints ignored with GWT, Eclipse, and Java 1.6.0_14?

Question

After upgrading to Java 1.6.0_14, a GWT application in Eclipse no longer stops at breakpoints even though Eclipse shows that the breakpoints are active. Are there workarounds for this issue?

Answer 1

The JDK early release 6u18 fixes this issue - finally!

Answer 2

Well, I faced this issue and found why it did not work.

First of all please check that all modules listed in debug arguments contain entry points, that means in Module.gwt.xml you have declared <entry-point/> declaration. If at least one module is included in arguments for debugging but it doesn't have entry point eclipse plugin debug won't work. (Must have)

Also check that parameter "-startupUrl" with value stands before listed modules in debug arguments. (Nice to have)

Answer 3

I had the same problem and installed the latest version (JDK 1.6.0_16) and it is now fixed. One of the bugs fixed in 1.6.0_16 is that breakpoints were not working.

-Chris Novak

Answer 4

The error occurs commonly with JDK 1.6.0_14 and is probably not related to GWT. Swing apps also have faced similar issues before. Here are some relevant links:

Eclipse SWING app: breakpoint hit only after an uncaught exception is thrown

https://bugs.eclipse.org/bugs/show_bug.cgi?id=279137

Answer 5

This is a known issue with GWT and Eclipse. The current recommended workaround is to use Java 1.6.0_13 for debugging.