blob: edff125d84ab4a770c2489a45a5d3b11b101f488 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<TITLE>Debugging a program</TITLE>
<link rel="stylesheet" type="text/css" HREF="../book.css">
</HEAD>
<BODY BGCOLOR="#ffffff">
<h2>Debugging a program</h2>
<p>When you define a <a href="debug_launch.htm">launch configuration</a> for
running a program, you can specify which modes (run and/or debug) your program
supports.&nbsp; If you support debug mode, then you need to implement a debug
model and UI that allow users to interact with your programs under debug.&nbsp;
The core platform debug plug-in provides support for:</p>
<ul>
<li> a generic debug model</li>
<li>debug
events and listeners</li>
<li>breakpoint management</li>
<li>expression management&nbsp;</li>
</ul>
<p>The debug UI plug-in provides utility classes for implementing debug user
interfaces.</p>
<p>Since it's difficult to discuss generic debugging in any meaningful detail,
we'll review the platform debug model and UI classes from the perspective of the
Java debugger.</p>
<p><a href="../hglegal.htm"><img border="0" src="../ngibmcpy.gif" alt="Copyright IBM Corporation and others 2000, 2003." border="0" width="324" height="14"></a></p>
</BODY>
</HTML>