I am busy trying to upgrade our GWT project to use the 1.1.0 release
and got this error. Our code was working perfectly with 1.0.21.
Analyzing permutation #1
[ERROR] Unexpected internal compiler error
com.google.gwt.dev.jjs.impl.InternalCompilerException: Error during
dispatch
at
com.google.gwt.dev.jjs.impl.GenerateJavaAST$JavaASTGenerationVisitor.dispatch(GenerateJavaAST.java:286)
at
com.google.gwt.dev.jjs.impl.GenerateJavaAST$JavaASTGenerationVisitor.dispProcessStatement(GenerateJavaAST.java:318)
at
com.google.gwt.dev.jjs.impl.GenerateJavaAST$JavaASTGenerationVisitor.processMethod(GenerateJavaAST.java:1094)
at
com.google.gwt.dev.jjs.impl.GenerateJavaAST$JavaASTGenerationVisitor.processType(GenerateJavaAST.java:253)
at
com.google.gwt.dev.jjs.impl.GenerateJavaAST.exec(GenerateJavaAST.java:1814)
at
com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compile(JavaToJavaScriptCompiler.java:267)
at
com.google.gwt.dev.GWTCompiler.realizePermutation(GWTCompiler.java:590)
at
com.google.gwt.dev.GWTCompiler.compilePermutations(GWTCompiler.java:338)
at com.google.gwt.dev.GWTCompiler.distill(GWTCompiler.java:287)
at com.google.gwt.dev.GWTCompiler.run(GWTCompiler.java:621)
at com.google.gwt.dev.GWTCompiler.main(GWTCompiler.java:189)
Caused by: java.lang.NullPointerException
at
com.google.gwt.dev.jjs.impl.GenerateJavaAST$JavaASTGenerationVisitor.processStatement(GenerateJavaAST.java:1222)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.google.gwt.dev.jjs.impl.GenerateJavaAST$JavaASTGenerationVisitor.dispatch(GenerateJavaAST.java:274)
... 10 more
Anyone know how to work around this?
I am about to start the tedious process of commenting out sections of
our 13k lines of client code to isolate the problem :(
Cheers
David
for (int i = 0; ; ++i) {
}
I'll get this fix into the next release.
Thanks,
Scott
Yep putting in a "true" instead of the empty tests solved the problem!