Mercurial > hg > graal-compiler

view agent/doc/hsdb.html @ 10988:cd54c7e92908

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
8015660: Test8009761.java "Failed: init recursive calls: 24. After deopt 25" Summary: Windows reserves and only partially commits thread stack. For detecting more thread stack space for execution, Windows installs one-shot page as guard page just before the current commited edge. It will trigger STACK_OVERFLOW_EXCEPTION when lands on last 4 pages of thread stack space. StackYellowPages default value is 2 on Windows (plus 1 page of StackRedPages, 3 pages guarded by hotspot) so the exception happens one page before Yellow pages. Same route executed second time will have one more page brought in, this leads same execution with different stack depth(interpreter mode). We need match Windows settings so the stack overflow exception will not happen before Yellow pages. Reviewed-by: dholmes Contributed-by: andreas.schoesser@sap.com
author minqi
date Tue, 18 Jun 2013 09:08:35 -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>