RFR(XS): 8008188: Add regression test for 8005875

Leonid Mesnik leonid.mesnik at oracle.com
Thu Feb 14 12:27:33 UTC 2013


This test should start failing in non-G1 baseline. Even 
"IgnoreUnrecognizedVMOptions" is added I think it should fail because of 
incompatible GC combinations.

Also I think that investigation parent process from child is not safe 
and make analysis harder if something going wrong.

Also there was a bug  15947151 - JDK6 JMAP -HEAP LOCKS post 6u29.
Here are comments from Kevin:

/@ Using Runtime.exec to launch a child process which then attaches back 
to the/
/@ parent to run diagnostics just sounds risky.  Diagnostics may need to 
/@ the parent JVM.  The child needs the parent to read buffers such that 
the /
/@ child may write.  Buffering usually lets this succeed, but there could/
/@ be some risk./

So I would prefer to avoid such schemes if we don't want to test them.


On 02/14/2013 04:51 AM, John Cuthbertson wrote:
> Hi Everyone,
> Can I have a couple of volunteers review the regression test for 
> 8005875 - the webrev can be found at: 
> http://cr.openjdk.java.net/~johnc/8008188/webrev.0/
> The test is very simple and issues "jcmd <pid> Thread.print" against 
> itself. With G1 and PGCT=0, and before the fix for 8005875, this 
> command crashes the VM.
> Testing:
> jdk8 build (b76) with fix for 8005875; jdk8 build (b71) without fix 
> for 8005875; Changed the test options to run the test with the invalid 
> flag -XX:+UseG2GC.
> Thanks,
> JohnC

Leonid Mesnik

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20130214/ee5c4351/attachment.htm>

More information about the hotspot-gc-dev mailing list