SDBG is the way to go for debugging, like they said. Keep in mind if the Chrome dev tools are open it will take over the breakpoints, and they are stated in Chrome dev tools. If Chrome dev tools are closed, and you opened debugging the browser with the SDBG Javascript debugger shortcut, then Eclipse is in charge of the break points, console output and trace inspection.
I'll create a video and guide here shortly. And talk about it at GWT Con. https://github.com/gwt-plugins/gwt-eclipse-plugin/projects/2 -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
