On Thu, Jun 16, 2011 at 17:52, Thomas Broyer <[email protected]> wrote:
> the browser should then stop at the exception and allow you to look at the
> snippet of code that caused it; there should be enough information there to
> point you to the corresponding JSNI method
Thanks for the fast reply. Ok, I tried that, did only work when
working with the compiled JS. Compiled as "detailed" it breaks here:
function
com_google_gwt_core_client_impl_StackTraceCreator$Collector_$makeException__Lcom_google_gwt_core_client_impl_StackTraceCreator$Collector_2Lcom_google_gwt_core_client_JavaScriptObject_2(){
try {
null.a();
}
catch (e) {
return e;
}
}
at the "null.a();". All code above in the stack is not from me and
part of the framework -- but i don't really get it and that wasn't too
helpful.
Actually, setting a breakpoint inside that JS-Exception and
investigating the arguments revealed it. I was calling "arc(...)" on a
Context2D of a canvas element and the arguments were arc(2.0, NaN,
...) and well, that won't work. Better stacktrace would have been
helpful, though.
H
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
