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) |
(→Overview) |
||
| Line 3: | Line 3: | ||
== Overview == | == Overview == | ||
| − | This page describes how you can take advantage of the remote Rhino debug support. | + | 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: | There are two pieces to make this work: | ||
#the server-side bits <code>org.eclipse.wst.jsdt.debug.rhino.debugger</code> and <code>org.eclipse.wst.jsdt.debug.transport</code> that are used to load scripts to be debugged, and | #the server-side bits <code>org.eclipse.wst.jsdt.debug.rhino.debugger</code> and <code>org.eclipse.wst.jsdt.debug.transport</code> that are used to load scripts to be debugged, and | ||
| − | #the client-side bits which | + | #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. | ||
== System Properties == | == System Properties == | ||
Revision as of 22:26, 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 |
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.