So, I've run across a very curious problem today, and I'm hoping that someone here might be able to offer some direction.
When trying to set breakpoints in the java source code using DevTools after entering Super Dev Mode, I was having the issue that the execution would simply steamroll right over the breakpoint without stopping. I tried to counter this by creating a static JSNI function that simply calls "debugger" in native JS, and then inserting a call to that function in the java code. Now, here's where it gets weird. Code execution reaches the call to the debug function and pauses just like it should -- BUT -- the highlighted line where the execution is paused is several lines *below* the line it should be on, sometimes even in the middle of a completely unrelated function. The call stack shows the correct function name, though it has the wrong line number, and stepping through the code shows that it is progressing through the code correctly despite the highlighted lines being wrong. This makes me think the initial problem was more to do with the debugger thinking the breakpoint I'd set wasn't on the line I set it on, and therefore never registered it being hit. So, is there anything I can do to figure out why the execution and call stack would be correct but the source code be incorrectly highlighted? Is there a way that the source maps could be out of sync or somehow offset? Thanks in advance, Roger -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
