Remote Debugging on Tizen

Today Developer Tools front-end can attach to a remotely running Tizen Crosswalk application for debugging. For this scenario to work, you should start your remote Tizen application enabling remote debugging. Generally, there are two steps. First open the remote-debugging-mode of xwalk service. Then make the specified Crosswalk application debuggable. The follow are the detail steps.

(1) The remote-debugging-mode of xwalk service with the specified port can be opened by the either following methods:

Using ”xwalkctl -d PORT_NUMBER“ to enable/disable remote-debugging-mode. This is the recommend method. Usage:

xwalkctl -d 9222 #enabled remote debugging at port '9222'
xwalkctl -d 0    #disable remote debugging.

Or， you can modify xwalk service configure file and restart xwalk service. Add the remote-debugging-port command line switch: --remote-debugging-port=9222 to "/usr/lib/systemd/user/xwalk.service" and restart the xwalk service.

(2) After remote-debugging-mode of xwalk is opened, you can enable remote debugging for an application with command:

app_launcher -s APP_ID -d

Only this application can be debugged, other applications are kept unaffected.

And now you can navigate to http://remote_device_ip:port from your host Chrome and attach to any of the discovered Tizen applications for debugging.

You can also use "sdb forward <local_port> <remote_port>" to forward socket connections

For example:

sdb forward tcp:9222 tcp:9222

Then navigate to http://localhost:9222