view src/share/tools/LogCompilation/README @ 1716:be3f9c242c9d

6948538: CMS: BOT walkers can fall into object allocation and initialization cracks Summary: GC workers now recognize an intermediate transient state of blocks which are allocated but have not yet completed initialization. blk_start() calls do not attempt to determine the size of a block in the transient state, rather waiting for the block to become initialized so that it is safe to query its size. Audited and ensured the order of initialization of object fields (klass, free bit and size) to respect block state transition protocol. Also included some new assertion checking code enabled in debug mode. Reviewed-by: chrisphi, johnc, poonam
author ysr
date Mon, 16 Aug 2010 15:58:42 -0700
parents 07d449658fc7
children 2aff40cb4703
line wrap: on
line source

This is a very rough tool for parsing -XX:+LogCompilation output.
It's main purpose is to recreate output similar to
-XX:+PrintCompilation -XX:+PrintInlining output from a debug JVM.  It
requires a 1.5 JDK to build and simply typing make should build it.

It produces a jar file, logc.jar, that can be run on the
hotspot.log from LogCompilation output like this:

  java -jar logc.jar hotspot.log

This will produce something like the normal PrintCompilation output.
Adding the -i option with also report inlining like PrintInlining.

More information about the LogCompilation output can be found at 

http://wikis.sun.com/display/HotSpotInternals/LogCompilation+overview
http://wikis.sun.com/display/HotSpotInternals/PrintCompilation
http://wikis.sun.com/display/HotSpotInternals/LogCompilation+tool