Unable to connecto to Chrome

[Eduardo Guardiola]

I can debug my project using GWT 2.7 without any problem. But when i try to lauch SDBG the same way as related in the video tutorial i get an Eclipse's error popup  saying: Unable to connect to Chrome: connect: Address is invalid on local machine, or port is not valid on remote machine.

Chrome window is opened and my app is compiled and loaded but SDBG fails after 99% when Launching Delegate...

¿Any tip?

[Ivan Markov]

I need more details to diagnose the problem.

Would you send me your Eclipse error log so I can see if there are any errors/exceptions in there?

You can retrieve it from Help -> About Eclipse -> Installation Details -> View error log

Another useful thing would be if you enable Tracing for SDBG from Window -> Preferences -> Tracing -> Enable tracing and then send me the trace log as well (once you try to launch the app at least once).

Please enable all SDBG tracing options before launching the app - thanks!

[Eduardo Guardiola]

Thanks. 

Check out attached files.

[Eduardo Guardiola]

And nothing related to SDBG was on eclipse log file.

[Ivan Markov]

This looks really, really strange.

I can see in the code where it fails, but there is no reasonable explanation why it fails.

OK it sounds strange but the following question: did you update your Java runtime recently? If so, did you restart your PC after that? If not, please restart it and try again. Thanks.

Please let me know the outcome. If it does not work, I'll put some additional tracing in-place to see exactly what is going on. It seems the "host" reported by Chrome main tab when launching the browser is not valid.

[Eduardo Guardiola]

I didn't update Java recently. Anyway i just rebooted but the problem persists. :-/

[Eduardo Guardiola]

Sorry. I was launching SDBG using a Run configuration instead Debug configuration. Now it runs fine. But now i see breakpoints does nothing. :-/

[Ivan Markov]

Thanks for the update. Well, it is still a bug, because If you launch it with "Run" then it should either work without complaining (but of course breakpoints will not be hit), or it should not even be present in the "Run configurations" dialog.

As for breakpoints not working - are you sure you have your breakpoints set in an event handler? Because if they are in the onModuleLoad() code, they won't be hit for sure (a racing issue with the Chrome debugging protocol).

[Eduardo Guardiola]

Fixed on recent release.