Mercurial > hg > graal-jvmci-8

view agent/doc/hsdb.html @ 1047:beb8f45ee9f0

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
6889740: G1: OpenDS fails with "unhandled exception in compiled code" Summary: Incorrect code was being generated for the store operation in the null case of the aastore bytecode template. The bad code was generated by the store_heap_oop routine which takes a Register as its second argument. Passing NULL_WORD (0) as the second argument causes the value to be converted to Register(0), which is rax. Thus the generated store was "mov (dst), $rax" instead of "mov (dst), $0x0". Changed calls to store_heap_oop that pass NULL_WORD as the second argument to a new routine store_heap_oop_null. Reviewed-by: kvn, twisti
author johnc
date Thu, 29 Oct 2009 09:42:26 -0700
parents a61af66fc99e
children
line wrap: on
line source

<html>
<head>
<title>
SA HSDB GUI
</title>
</head>
<body>
<p>
Once the HSDB debugger has been launched, the threads list is displayed
if launched with debuggee options (pid or core) in command line. If
HSDB was launched without debuggee, empty screen is shown.
</p>
<p>File menu sub-menu options to attach, detach debuggee and exit tool.</p>
<p>Tools menu sub-menus include:</p>
  <ul>
  <li>browsing of the annotated stack memory ("Stack Memory" button). It
   is currently annotated with the following information:
   <ul>
   <li> method names of the Java frames and their extents (supporting
     inlined compiled methods)
   <li> locations and types of oops, found using the oop map information
     from compiled methods (interpreter oop maps coming soon)
   <li> if a Java frame was interrupted by a signal (e.g., because of a
     crash), annotates the frame with the signal name and number
   <li> interpreter codelet descriptions for interpreted frames
   </ul>
 <li> finding which thread or threads caused a crash (currently
   identified by the presence of a signal handler frame - solaris-only)
 <li> browsing of oops using the Oop Inspector.
 <li> browsing of the java.lang.Thread object's oop.
 <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
 </ul>
<p>Windows sub-menu options include:</p>
 <ul>
 <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))
</ul>

</body>
</html>