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?
Asked
Active
Viewed 5,774 times
5 Answers
2
This is a known issue with GWT and Eclipse. The current recommended workaround is to use Java 1.6.0_13 for debugging.
Greg Bacon
- 134,834
- 32
- 188
- 245
-
I experienced this with Java 7 b59 too. Annoying. – akarnokd Jun 22 '09 at 13:06
-
Having the same issue with jdk-7u75-windows-x64. @akarnokd: How the blazes did you get your hands on Java 7 in 2009?!? That came out in mid-2011, didn't it? – Amos M. Carpenter Nov 18 '15 at 08:18
-
Early access builds, freely available then and now with Java 9. – akarnokd Nov 18 '15 at 08:29
2
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
-
Fron that Eclipse bug, it seems a workaround inside 6u14 is to use the JVM option: -XX:+UseParallelGC – gojomo Jul 24 '09 at 21:07
2
The JDK early release 6u18 fixes this issue - finally!
Denilson Sá Maia
- 47,466
- 33
- 109
- 111
jah
- 2,056
- 1
- 18
- 35
0
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
sth
- 222,467
- 53
- 283
- 367
0
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)
alex.b
- 1,448
- 19
- 23