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