Wednesday, July 1, 2015

Problems Remote Debugging with SourceMaps in SuperDevMode

Using Chrome, I've got SDM working locally - reloading the page trips the CodeServer I have running in Eclipse, and the sourcemaps are accessible in Chrome via 127.0.0.1:9876 in the sources tab.

However, I wanted to try access from another machine.  So I made the changes to my setup that are mentioned on the web:
  • I added "-bindAddress 0.0.0.0" to the SuperDevMode launch program arguments.
  • I added <set-configuration-property name="devModeUrlWhitelistRegexp" value="http://.*" /> to the GWT Project and rebuilt it
  • I tried opening http://application-server:port/?superdevmode=ip:port rather than simply http://application-server:port (though this one didn't seem to make a difference)

With the above approach, I am able to run the CodeServer remotely.  I see CodeServer run in Eclipse on the host machine, and the page loads on the client machine and appears to work fine.  However, there are no sourcemaps available in Chrome on the remote machine (or any other browser).  I tried disabling the firewall with no change.


Host machine: OpenSUSE 13.1, Chrome 43.0.2357.65
Client machine Windows 7 SP1 x64, 43.0.2357.130

Can anyone else confirm this is broken?  If so I will file an issue on GitHub.

(Note: I am planning to post a separate thread regarding SDM not working locally in Firefox, so please limit discussion here to remote access issues.)





--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment