Skip to main content
Jump to: navigation, search

JSDT/Debug/Rhino

< JSDT‎ | Debug
Revision as of 16:44, 14 January 2011 by Michael Rennie.ca.ibm.com (Talk | contribs) (Launch Options)

JSDT Debug
Website
Download
Community
Mailing ListForumsIRCmattermost
Issues
OpenHelp WantedBug Day
Contribute
Browse SourceProject Set File

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 Options

The options on the Main tab allow you to specify the script you want to debug and the parameters use to configure the Rhino interpreter. The default options specified for a new configuration will provide you with the most general debugging experience, but you can tailor how the interpreter runs to reproduce specific scenarios.

There are a few options for Rhino which are as follows:

Script 
The script option is required and points to the JavaScript file in you workspace that you wish to debug. The file is checked for existence, so a manually entered path will be validated
ECMA script version to interpret with 
This option allows you to set the ECMA compliance level that Rhino will interpret the script using. For more information on how Rhino uses this option see this link about the option to Rhino and this link about JavaScript language levels.
Rhino optimization level 
Rhino can make certain optimizations when it interprets the script. To find out more about what each optimization means / does check this link.
Strict mode 
This option puts Rhino in strict mode. When in strict mode Rhino will treat some warnings as errors and will report all warnings. It can be a challenge to debug scripts in strict mode, as many more problems are found, most of which terminate interpreting the script.
Log interpreter exceptions 
In certain cases, usually a fatal problem from the interpreter, exceptions will be thrown from Rhino. This option allows them to be forwarded to the Eclipse error log.

Include Paths

The Include tab for a Rhino configuration allows you to quickly and easily add additional scripts to be run before the main script.

You have the option to add one or more scripts from the workspace or from the local or extended file system.

Using the Up and Down buttons you can place the scripts in the order you would like them to be run. The script at the top of the listing will be run first. You can also use the Remove button to remove the selected included scripts from the listing.

Any scripts that are added to the include path also have their containing folder automatically added to the source lookup path. For example if you added the script /home/user/myscript.js to the include path, the folder entry for /home/user/ would be added to the source lookup path for you automatically.

Source Lookup

The Source tab allows you to customize where the launch will look for your source. This tab is automatically updated to track the script specified on the Main tab as well as entries on the Include tab.

Any automatically added entries can be changed / removed as you like and and new entries can be added from one of the following locations:

  • Archive
  • External Archive
  • File System Directory
  • Java Classpath Variable
  • Java Library
  • Java Project
  • Project
  • Working Set
  • Workspace
  • Workspace Folder

To modify the source lookup path simply use the Add..., Remove... or Edit... buttons. The Default project source lookup entry cannot be modified, as it it directly tied to the script specified on the Main tab. But you can modify and edit any child entries of the Default project entry.

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.

The complete specification for the RDWP can be found here.

Back to the top