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"
(→Single-click Launching) |
|||
Line 1: | Line 1: | ||
{{JSDT-Debug}} | {{JSDT-Debug}} | ||
− | == | + | == Local Rhino Debugging == |
− | New to 1.3 is the ability to locally launch and debug JavaScript file(s) using Rhino. | + | New to 1.3 is the ability to locally launch and debug JavaScript file(s) using Rhino. This new launching support includes context-sensitive launching from the platform and automatic source / script path updating. |
+ | |||
+ | The related New and Noteworthy entry is [http://www.eclipse.org/webtools/development/news/3.3M2/sourceediting.php here]. | ||
+ | |||
+ | ==== Launch Configurations ==== | ||
+ | |||
+ | ==== Include Paths ==== | ||
+ | |||
+ | ==== Launch Options ==== | ||
== Embedding the Rhino Debugger == | == Embedding the Rhino Debugger == |
Revision as of 14:52, 14 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
Local Rhino Debugging
New to 1.3 is the ability to locally launch and debug JavaScript file(s) using Rhino. This new launching support includes context-sensitive launching from the platform and automatic source / script path updating.
The related New and Noteworthy entry is here.
Launch Configurations
Include Paths
Launch Options
Embedding the Rhino Debugger
One of the more powerful usages of the Rhino debug support is that it can easily be embedded into your existing server. Embedding the Rhino Debugger allows you to remotely debug the loading and execution of scripts from the Eclipse IDE.
To learn how to embed the Rhino Debugger please go to this page.
Rhino Debug Wire Protocol
To provide support for the Rhino interpreter, we had to create both sides of the coin - the debugger and the client. To facilitate communication between the debugger and the client we created an adapted version of v8 (JSON-based) packet communication.