2N/AOnce the HSDB debugger has been launched, the threads list is displayed
2N/Aif launched with debuggee options (pid or core) in command line. If
2N/AHSDB was launched without debuggee, empty screen is shown.
2N/A<
p>File menu sub-menu options to attach, detach debuggee and exit tool.</
p>
2N/A<
p>Tools menu sub-menus include:</
p>
2N/A <
li>browsing of the annotated stack memory ("Stack Memory" button). It
2N/A is currently annotated with the following information:
2N/A <
li> method names of the Java frames and their extents (supporting
2N/A inlined compiled methods)
2N/A <
li> locations and types of oops, found using the oop map information
2N/A from compiled methods (interpreter oop maps coming soon)
2N/A <
li> if a Java frame was interrupted by a signal (
e.g., because of a
2N/A crash), annotates the frame with the signal name and number
2N/A <
li> interpreter codelet descriptions for interpreted frames
2N/A <
li> finding which thread or threads caused a crash (currently
2N/A identified by the presence of a signal handler frame - solaris-only)
2N/A <
li> browsing of oops using the Oop Inspector.
<
li> Object Histogram and inspection of objects and liveness analysis therein.
<
li> Class Browser - view Java classes, bytecode disassembly,
or create .class files for selected classes
<
li> native disassembly (sparc, x86 only) and nmethod disassembly with annotations for safepoint details.
<
li> view -XX flags, System properties, VM version of debuggee
<
p>Windows sub-menu options include:</
p>
<
li> Windows sub-menu: Console window to run "CLHSDB" commands in GUI
<
li> Windows sub-menu: Debugger console of underlying native debugger (MS Windbg or dbx (if used))