59 lines
4.3 KiB
HTML
59 lines
4.3 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Full-Speed Debug" />
|
|
<meta name="abstract" content="The iSeries Java Virtual Machine (JVM) now supports "full-speed debugging". Prior to V5R3, enabling debugging meant disabling the Just-In-Time (JIT) compiler. Application performance suffered because many methods had to be run with the slow interpreter. This significant performance degradation was especially difficult for applications that could run for days before getting to the point where you wished to begin debugging." />
|
|
<meta name="description" content="The iSeries Java Virtual Machine (JVM) now supports "full-speed debugging". Prior to V5R3, enabling debugging meant disabling the Just-In-Time (JIT) compiler. Application performance suffered because many methods had to be run with the slow interpreter. This significant performance degradation was especially difficult for applications that could run for days before getting to the point where you wished to begin debugging." />
|
|
<meta name="DC.Relation" scheme="URI" content="jpdebuga.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzahafsdebug" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Full-Speed Debug</title>
|
|
</head>
|
|
<body id="rzahafsdebug"><a name="rzahafsdebug"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Full-Speed Debug</h1>
|
|
<div><p>The iSeries™ Java™ Virtual
|
|
Machine (JVM) now supports "full-speed debugging". Prior to V5R3, enabling
|
|
debugging meant disabling the Just-In-Time (JIT) compiler. Application performance
|
|
suffered because many methods had to be run with the slow interpreter. This
|
|
significant performance degradation was especially difficult for applications
|
|
that could run for days before getting to the point where you wished to begin
|
|
debugging.</p>
|
|
<p>Full-speed debug allows you to run your application with all the performance
|
|
benefits of JIT compiled code without losing the ability to perform some of
|
|
the most common debugging activities, such as setting breakpoints, stepping
|
|
through code, and viewing local variables.</p>
|
|
<p>Since full-speed debug allows methods to be JIT compiled, there are a couple
|
|
of limitations on debugging: </p>
|
|
<ul><li>Step operations on return statements do not work if the caller is compiled
|
|
code. </li>
|
|
<li>Watchpoints only trigger in non-compiled methods that modify the watched
|
|
field. </li>
|
|
</ul>
|
|
<div class="note"><span class="notetitle">Note:</span> This feature is only supported for debuggers that use the Java Debug
|
|
Wire Protocol (JDWP) to perform debugging operations. The system debugger
|
|
currently does not support full-speed debug. </div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="jpdebuga.htm" title="The Java Platform Debugger Architecture (JPDA) consists of the JVM Debug Interface/JVM Tool Interface, the Java Debug Wire Protocol, and the Java Debug Interface. All these parts of the JPDA enable any front end of a debugger that uses the JDWP to perform debugging operations. The debugger front end can either run remotely or run as an iSeries application.">Java Platform Debugger Architecture</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |