Mercurial > hg > graal-jvmci-8
view agent/doc/hsdb.html @ 20228:f72d8917322a
8050978: Fix bad field access check in C1 and C2
Summary: JCK8 test vm/constantpool/accessControl/accessControl004/accessControl00402m3/accessControl00402m3.html fails with -Xbatch -Xcomp due to bad field access check in C1 and C2. Fix: In ciField::ciField(), just before the canonical holder is stored into the _holder variable (and which is used by ciField::will_link()) perform an additional access check with the holder declared in the class file. If this check fails, store the declared holder instead and ciField::will_link() will bail out compilation for this field later on. Then, the interpreter will throw an PrivilegedAccessException at runtime.
Reviewed-by: kvn, vlivanov
Contributed-by: andreas.schoesser@sap.com
author | goetz |
---|---|
date | Fri, 18 Jul 2014 09:04:01 +0200 |
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>