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.
Difference between revisions of "JSDT/Debug/Rhino/Embedding Rhino Debugger"
(→Overview) |
|||
| Line 11: | Line 11: | ||
The server-side requires a bit of configuration and some custom coding to get working as you want, but the client-side works the same way as Java remote debugging; such that you specify the address and port to connect to and start debugging. | The server-side requires a bit of configuration and some custom coding to get working as you want, but the client-side works the same way as Java remote debugging; such that you specify the address and port to connect to and start debugging. | ||
| − | == | + | == Setting up the Rhino Debugger == |
| − | == | + | === The rhino.debug System Property === |
| − | == | + | === Example Code === |
| + | |||
| + | == Connecting to a Remote Rhino Debugger == | ||
| + | |||
| + | To connect to a remote Rhino debugger is fairly straightforward. | ||
| + | |||
| + | The first step is to create a new Remote JavaScript launch configuration. To do so you must open the launch dialog in Debug mode, as the Remote JavaScript launch configuration does not apply to the Run mode. | ||
| + | |||
| + | With the dialog open, simply double-click the Remote JavaScript launch configuration to create a new one and fill in the required fields. | ||
| + | |||
| + | [[Image:Remote_js_config.png]] | ||
| + | |||
| + | To connect to a remote Rhino debugger you will have to select '''Mozilla Rhino - Attaching Connector''' as the connector and fill in the host name and the port number of the host where the debugger is running. | ||
| + | |||
| + | == Testing Remote Rhino Locally == | ||
Revision as of 22:37, 10 January 2011
| JSDT Debug | |
| Website | |
| Download | |
| Community | |
| Mailing List • Forums • IRC • mattermost | |
| Issues | |
| Open • Help Wanted • Bug Day | |
| Contribute | |
| Browse Source • Project Set File |
Contents
Overview
This page describes how you can take advantage of the remote Rhino debug support from both the client and server side. It provides in-depth details on how to set up Rhino debugging in your server and how you can connect to a server already running the Rhino debugger.
There are two pieces to make this work:
- the server-side bits
org.eclipse.wst.jsdt.debug.rhino.debuggerandorg.eclipse.wst.jsdt.debug.transportthat are used to load scripts to be debugged, and - the client-side bits which is the Eclipse integration and UI
The server-side requires a bit of configuration and some custom coding to get working as you want, but the client-side works the same way as Java remote debugging; such that you specify the address and port to connect to and start debugging.
Setting up the Rhino Debugger
The rhino.debug System Property
Example Code
Connecting to a Remote Rhino Debugger
To connect to a remote Rhino debugger is fairly straightforward.
The first step is to create a new Remote JavaScript launch configuration. To do so you must open the launch dialog in Debug mode, as the Remote JavaScript launch configuration does not apply to the Run mode.
With the dialog open, simply double-click the Remote JavaScript launch configuration to create a new one and fill in the required fields.
To connect to a remote Rhino debugger you will have to select Mozilla Rhino - Attaching Connector as the connector and fill in the host name and the port number of the host where the debugger is running.