> The biggest problem is that Chrome doesn't give ANY stacktrace, nor does > it allow for breaking on error. I've tried compiling with 'pretty' so I > could breakpoint on error and figure out the offending code, but it won't > work. >
Chrome can pause on any JavaScript error thrown, caught and uncaught ones. Go to the sources tab in Chrome DevTools, hit the small "pause" icon on the right side and check the "pause on caught exceptions" checkbox. Chrome should then pause on ANY exception thrown, so you would need to check if its the "RangeError: Maximum call stack size exceed" or not. If Chrome still does not pause even though you get the mentioned error then you have to talk to the Chrome guys by opening an issue to ask them how to debug that situation. Adding lots of log statements doesn't seem to be the solution. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/b1a7464c-c160-4e2f-b747-f996e259a6e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
