[gwt-contrib] Re: internal compiler error with latest SNAPSHOT

2016-07-20 Thread 'Roberto Lublinerman' via GWT Contributors
I filed a bug with a minimal repro at https://github.com/gwtproject/gwt/issues/9379 and uploaded a fix for review at https://gwt-review.googlesource.com/#/c/15450 On Wed, Jul 20, 2016 at 11:23 AM, Roberto Lublinerman wrote: > Could you guys file an issue for this to keep track of it? > > On Wed,

[gwt-contrib] Re: internal compiler error with latest SNAPSHOT

2016-07-20 Thread 'Roberto Lublinerman' via GWT Contributors
Could you guys file an issue for this to keep track of it? On Wed, Jul 20, 2016 at 10:34 AM, Roberto Lublinerman wrote: > It should read setJsOverlay() but that would not fix the error. I think I > understand why it might be happening but it would be nice if we have a > small repro case. > > On

[gwt-contrib] Re: internal compiler error with latest SNAPSHOT

2016-07-20 Thread 'Roberto Lublinerman' via GWT Contributors
It should read setJsOverlay() but that would not fix the error. I think I understand why it might be happening but it would be nice if we have a small repro case. On Wed, Jul 20, 2016 at 6:42 AM, Thomas Broyer wrote: > +rluble > > Could you set a breakpoint in JjsUtils trying to understand what

[gwt-contrib] Re: internal compiler error with latest SNAPSHOT

2016-07-20 Thread Thomas Broyer
+rluble Could you set a breakpoint in JjsUtils trying to understand what causes the NPE? (what is null, which method is being processed, and what it looks like in your code) Reading the code, I wonder if https://github.com/gwtproject/gwt/blob/master/dev/core/src/com/google/gwt/dev/jjs/impl/Jjs