Architecture Overview
The JavaTM Platform Debugger Architecture is structured as follows: Components Debugger Interfaces
/ |--------------|
/ | |
----( |--------------| <------- - Java VM Debug Interface
\ | |
\ |--------------|
/ |
-( | <--------------- - Java Debug Wire Protocol
\ |
|--------------|
| |
|--------------| <------- - Java Debug Interface
| |
|--------------|
What is the Java Platform Debugger Architecture (JPDA)?
JPDA is a multi-tiered debugging architecture that allows tools developers to easily create debugger applications which run portably across platforms, implementations and SDK versions.
JPDA consists of three layers:
- - Java VM Debug Interface
- Defines the debugging services a VM provides.
- - Java Debug Wire Protocol
- Defines the communication between and debugger processes.
- - Java Debug Interface
- Defines a high-level Java language interface which tool developers can easily use to write remote debugger applications.
Reference implementation
In addition to the specification of these interfaces, Sun Microsystems also provides a reference implementation, which consists of:
- JVMDI implementations on multiple Sun VMs (see VM documentation).
- A which uses JVMDI to implement the debuggee side of JDWP.
- A which uses the debugger side of JDWP to implement JDI.
- Two simple example debugger applications which are built on JDI.
This provides a layered implementation in which any layer may be substituted.
Using JPDA
A debugger developer may hook into JPDA at any layer. Since the JDI is the highest level and easiest to use we encourage developers to use this interface. Suppose a company develops a debugger using JDI. They can use it with the reference implementation and it will automatically work with the VMs and platforms Sun supports. It can also work, for example, with the reference implementation front-end and a debuggee running another company's VM that implements JDWP (which might use or by-pass JVMDI).
Some debuggers are built on top of lower layers, JDWP (for example if the front-end is not written in the Java language) or JVMDI (for specialized debuggers which need low-level functionality).
Components
debuggee
The debuggee is the process being debugged, it consists of the application being debugged (not shown), the running the application and the of the debugger.
Java Virtual Machine (VM)
This refers to the VM running the application being debugged.
The debugger architecture is being designed for use in wide spectrum of VM implementations.
The VM implements the Java Virtual Machine Debug Interface ().
back-end
The back-end of the debugger is responsible for communicating requests from the debugger to the debuggee and for communicating the response to these requests (including desired events) to the front-end. The back-end communicates with the front-end over a using the Java Debug Wire Protocol (). The back-end communicates with the debuggee VM using the Java Virtual Machine Debug Interface ().
It is clear from experience that debugger support code, running on the debuggee and written in Java, contends with the debuggee in ways that cause hangs and other undesired behavior. Thus, the back-end is native code. This, in turn, implies that the be a pure native interface.
communications channel
The communications channel is the link between the and ends of the debugger. The transport mechanism used is unspecified; possible mechanisms include: sockets, serial lines, and shared memory. However, the format and semantics of the serialized bit-stream flowing over the channel is specified by the Java Debug Wire Protocol ().
front-end
The debugger front-end implements the high-level Java Debug Interface (). The front-end uses the information from the low-level Java Debug Wire Protocol ().
User Interface (UI)
Debugger Interfaces
A native interface implemented by the .
Defines the services a VM must provide for debugging. Includes requests for information (for example, current stack frame), actions (for example, set a breakpoint), and notification (for example, when a breakpoint has been hit). A debugger may make use of VM information other than this (for example, Java Native Interface (JNI)), but this is the source of all debugger specific information.
Specifying the VM Interface allows any VM implementor to plug easily into the debugging architecture. It also allows alternate communication channel implementations. VM implementations which do not adhere to this interface can still provide access via the Java Debug Wire Protocol ().
See also:
Defines the format of information and requests transferred between the process and the debugger . It does not define the transport mechanism (socket, serial line, shared memory, ...).
The specification of the protocol allows the debuggee and debugger front-end to run under separate VM implementations and/or on separate platforms. It also allows the front-end to be written in a language other than Java, or the debuggee to be non-native (e.g. Java).
Information and requests are roughly at the level of the Java Virtual Machine Debug Interface (), but will include additional information and requests necessitated by bandwidth issues, examples include information filtering and batching.
See also:
A 100% Java interface implemented by the .
Defines information and requests at a user code level.
While debugger implementors could directly use the Java Debug Wire Protocol () or Java Virtual Machine Debug Interface (), this interface greatly facilitates the integration of debugging capabilities into development environments. We recommend the JDI layer for all debugger development.
See also:
