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/JavaScript Debug Interface"
| (3 intermediate revisions by one other user not shown) | |||
| Line 4: | Line 4: | ||
The JSDI specifies a format in which a debugger can communicate with a running virtual machine (VM). This includes describing methods to [[#Connectors|connect]] the VM and debugger, what [[#Events|events]] the vm can send to describe changes in state, what [[#Requests|requests]] the debugger can make to alter the state and what [[#Values|values]] can be used to describe the state. | The JSDI specifies a format in which a debugger can communicate with a running virtual machine (VM). This includes describing methods to [[#Connectors|connect]] the VM and debugger, what [[#Events|events]] the vm can send to describe changes in state, what [[#Requests|requests]] the debugger can make to alter the state and what [[#Values|values]] can be used to describe the state. | ||
| + | |||
| + | The JSDI specification is based on the [http://java.sun.com/j2se/1.4.2/docs/guide/jpda/jdi/|Sun Java Debug Interface specification]. | ||
== Connectors == | == Connectors == | ||
| Line 13: | Line 15: | ||
# '''Attaching Connector''' - Connects to an already running VM | # '''Attaching Connector''' - Connects to an already running VM | ||
# '''Launching Connector''' - Launches a VM and connects to it | # '''Launching Connector''' - Launches a VM and connects to it | ||
| + | |||
| + | See package ''org.eclipse.wst.jsdt.debug.core.jsdi.connect'' | ||
== Events == | == Events == | ||
| − | The VM will fire events to | + | The VM will fire events to inform the debugger of changes in state. The following events can be send by the VM: |
| − | + | * VM Death | |
| − | + | * VM Disconnect | |
| − | VM Death | + | * Breakpoint |
| − | VM Disconnect | + | * Debugger Statement |
| − | Breakpoint | + | * Exception |
| − | Debugger Statement | + | * Script Load |
| − | Exception | + | * Step |
| − | Script Load | + | * Suspend |
| − | Step | + | * Thread Enter |
| − | Suspend | + | * Thread Exit |
| − | Thread Enter | + | |
| − | Thread Exit | + | |
| + | See package ''org.eclipse.wst.jsdt.debug.core.jsdi.event'' | ||
== Requests == | == Requests == | ||
| Line 36: | Line 39: | ||
The debugger can create and send requests to the VM through the JSDI to get more information on the state of the VM or to modify it. The following types of requests are supported: | The debugger can create and send requests to the VM through the JSDI to get more information on the state of the VM or to modify it. The following types of requests are supported: | ||
| − | VM Death | + | * VM Death |
| − | VM Disconnect | + | * VM Disconnect |
| − | + | * Breakpoint | |
| − | Breakpoint | + | * Debugger Statement |
| − | Debugger Statement | + | * Exception |
| − | Exception | + | * Script Load |
| − | Script Load | + | * Step |
| − | Step | + | * Suspend |
| − | Suspend | + | * Thread Enter |
| − | Thread Enter | + | * Thread Exist |
| − | Thread | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| + | See package ''org.eclipse.wst.jsdt.debug.core.jsdi.request'' | ||
== Values == | == Values == | ||
| Line 65: | Line 65: | ||
* Number | * Number | ||
* String | * String | ||
| + | |||
| + | See package ''org.eclipse.wst.jsdt.debug.core.jsdi'' | ||
| + | |||
| + | [[Category:JSDT]] | ||
Latest revision as of 12:48, 8 June 2010
| JSDT Debug | |
| Website | |
| Download | |
| Community | |
| Mailing List • Forums • IRC • mattermost | |
| Issues | |
| Open • Help Wanted • Bug Day | |
| Contribute | |
| Browse Source • Project Set File |
Contents
Overview
The JSDI specifies a format in which a debugger can communicate with a running virtual machine (VM). This includes describing methods to connect the VM and debugger, what events the vm can send to describe changes in state, what requests the debugger can make to alter the state and what values can be used to describe the state.
The JSDI specification is based on the Java Debug Interface specification.
Connectors
A connector is a method of connecting a debugger and a VM. Connectors must provide an ID and may have a name and description. To customize the behaviour of the connector a map of arguments may be provided, mapping string argument keys to their values.
JSDI specifies three forms of connectors
- Listening Connector - When launched, waits for a vm to connect
- Attaching Connector - Connects to an already running VM
- Launching Connector - Launches a VM and connects to it
See package org.eclipse.wst.jsdt.debug.core.jsdi.connect
Events
The VM will fire events to inform the debugger of changes in state. The following events can be send by the VM:
- VM Death
- VM Disconnect
- Breakpoint
- Debugger Statement
- Exception
- Script Load
- Step
- Suspend
- Thread Enter
- Thread Exit
See package org.eclipse.wst.jsdt.debug.core.jsdi.event
Requests
The debugger can create and send requests to the VM through the JSDI to get more information on the state of the VM or to modify it. The following types of requests are supported:
- VM Death
- VM Disconnect
- Breakpoint
- Debugger Statement
- Exception
- Script Load
- Step
- Suspend
- Thread Enter
- Thread Exist
See package org.eclipse.wst.jsdt.debug.core.jsdi.request
Values
The following value types are specified by the JSDI.
- Null
- Undefined
- Object Reference
- Object reference
- Array reference
- Function reference
- Boolean
- Number
- String
See package org.eclipse.wst.jsdt.debug.core.jsdi