1 <html>
2 <head>
3 <title>
4 SA HSDB GUI
5 </title>
6 </head>
7 <body>
8 <p>
9 Once the HSDB debugger has been launched, the threads list is displayed
10 if launched with debuggee options (pid or core) in command line. If
11 HSDB was launched without debuggee, empty screen is shown.
12 </p>
13 <p>File menu sub-menu options to attach, detach debuggee and exit tool.</p>
14 <p>Tools menu sub-menus include:</p>
15 <ul>
16 <li>browsing of the annotated stack memory ("Stack Memory" button). It
17 is currently annotated with the following information:
18 <ul>
19 <li> method names of the Java frames and their extents (supporting
20 inlined compiled methods)
21 <li> locations and types of oops, found using the oop map information
22 from compiled methods (interpreter oop maps coming soon)
23 <li> if a Java frame was interrupted by a signal (e.g., because of a
24 crash), annotates the frame with the signal name and number
25 <li> interpreter codelet descriptions for interpreted frames
26 </ul>
27 <li> finding which thread or threads caused a crash (currently
28 identified by the presence of a signal handler frame - solaris-only)
29 <li> browsing of oops using the Oop Inspector.
30 <li> browsing of the java.lang.Thread object's oop.
31 <li> Object Histogram and inspection of objects and liveness analysis therein.
32 <li> Class Browser - view Java classes, bytecode disassembly,
33 or create .class files for selected classes
34 <li> native disassembly (x86 only) and nmethod disassembly with annotations for safepoint details.
35 <li> view -XX flags, System properties, VM version of debuggee
36 </ul>
37 <p>Windows sub-menu options include:</p>
38 <ul>
39 <li> Windows sub-menu: Console window to run "CLHSDB" commands in GUI
40 <li> Windows sub-menu: Debugger console of underlying native debugger (MS Windbg or dbx (if used))
41 </ul>
42
43 </body>
44 </html>