cess or core and also the folder where
the Debugging Tools for Windows are
installed on the machine, for example:
to the Java executable and then we can
launch HSDB as follows:
set PATH= d:\java\jdk1.7.0_03\bin\
server;d:\windbg;%PATH%
java -Dsun.jvm.hotspot.debugger.
useProcDebugger=true -classpath
/java/jdk1.7.0/lib/sa-jdi.jar
sun.jvm.hotspot.HSDB
Set the PATH environment variable
and then launch HSDB as follows:
java -Dsun.jvm.hotspot.debugger.
use WindbgDebugger=true -classpath
d:\java\jdk1.7.0_03\lib\sa-jdi.jar
sun.jvm.hotspot.HSDB
These launch commands bring up the
HSDB GUI tool, as shown in Figure 1.
We need to set the same environment variables for CLHSDB as we did for
HSDB. Use the following command to
launch this tool on Microsoft Windows:
java -Dsun.jvm.hotspot.debugger.
use WindbgDebugger=true -classpath
d:\java\jdk1.7.0_03\lib\sa-jdi.jar
sun.jvm.hotspot.CLHSDB
JAVA IN ACTION
CLHSDB offers almost all the features
that the GUI version of the tool offers.
On an Oracle Solaris or Linux
machine, we just need to set SA_JAVA
ABOUT US
Figure 1
Figure 3
Figure 5
blog
