<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<title>Java(tm) Debug Interface</title>
</head>
<body>
The Java<sup><font size="-2">TM</font></sup>
Debug Interface (JDI) is a high level Java
API providing information useful for debuggers and similiar
systems needing access to the running state of a (usually remote)
virtual machine.
<p>
The JDI provides introspective
access to a running virtual machine's state, Class, Array,
Interface, and primitive types, and instances of those
types.
<P>
The JDI also provides explicit control over
a virtual machine's execution. The ability to suspend
and resume threads, and to set breakpoints, watchpoints, ...
Notification
of exceptions, class loading, thread creation...
The ability to inspect a suspended thread's state,
local variables, stack backtrace...
<p>
JDI is the highest-layer of the Java Platform Debugger Architecture (JPDA).
For more information on the Java Platform Debugger Architecture, see the
<a href="{@docRoot}/technotes/guides/jpda/index.html">
Java Platform Debugger Architecture documentation</a>
for this release and the
<p>
<font size="+1"><b>Global Exceptions:</b></font>
<p>
This section documents exceptions which apply to the entire API and are thus
not documented on individual methods.
<blockquote>
<p>
<p>
virtual machines.
<p>
<p>
-- unless null is explicitly mentioned as a valid parameter.
<p>
</blockquote>
NOTE: The exceptions below may be thrown whenever the specified
conditions are met but a guarantee that they are thrown only
exists when a valid result cannot be returned.
<blockquote>
<p>
<p>
<p>
<p>
VM has run out of memory.
<p>
<p>
if the mirrored object has been garbage collected.
<p>
if the mirrored type has been unloaded.
</blockquote>
</body>
</html>