- Run the Chrome instance that you’ll be debugging remotely with the remote debugging command line switch: chrome.exe --remote-debugging-port=9222 --user-data-dir=remote-profile. It’s essential that you use a different instance of Chrome for the remote session and that’s why we run it with the --user-data-dirargument.
- Navigate to the pages you intend to debug.
- Now run a regular (client) Chrome instance and navigate to http://localhost:9222 there.
You’ll see a number of links that will bring you to the remote debugging sessions for the corresponding pages. Click them and enjoy debugging your Chrome pages over the wire:
“We implemented the remote debugging infrastructure in the WebKit repository (or as we say “upstream”), so that other WebKit port owners could expose remote debugging capabilities with a minimal effort. See more information on remote debugging in WebKit blog post,” informs Google.
For more information on the remote debugging and Chrome Developer Tools in general, see documentation page.
[Source: Chromium blog]