Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
JSDT/Debug/Using Google Chrome Debugger
Experimental Code
The Google Chrome debugger is in a experimental/propotype stage. The code is brittle and many use cases are not supported.
The Google Chrome debugger is in a experimental/propotype stage. The code is brittle and many use cases are not supported.
Overview
The Google Chrome debugger is an experiment to see if the JSDT debugger APIs can be hooked up to another debugger that was not co-developed with JSDI in mind. Google Chrome allows debuggers to connect as clients to WebInspector communicating with the v8 protocol.
Installing Components
Creating the Configuration
Once everything is installed and ready to go simply:
- open the launch configuration dialog in debug mode
- create a new JavaScript configuration
- select one of the Google Chrome launching connectors, fill in the fields as needed and press debug
If you chose the Google Chrome attaching connector, and did not check the option to automatically launch the browser, you will have to ensure that Chrome is running and was started with the correct command line parameters. For example:
chrome --remote-shell-port=9222
More information on starting the browser for client connections can be found [[1]].