Code Review request for new MallocMaxBytes option and fixed test (7030610, 7037122, 7123945)

[Ron Durbin]

All

 

I have a code review ready for:

 

WEBREV http://javaweb.us.oracle.com/~rdurbin/7030610-webrev/0-hsx25/

 

7030610 runtime/6878713/Test6878713.sh fails, Error. failed to clean up files after test.

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7030610

https://jbs.oracle.com/bugs/browse/JDK-7030610

 

7037122 runtime/6878713/Test6878713.sh is written incorrectly

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7037122

https://jbs.oracle.com/bugs/browse/JDK-7037122

 

7123945 runtime/6878713/Test6878713.sh require about 2G of

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7123945

https://jbs.oracle.com/bugs/browse/JDK-7123945

 

Summary: Add new diagnostic option -XX:MallocMaxBytes=NNN and fix 

Test6878713.sh.  Test6878713.sh is a security regression test with four different
failure modes. Three are documented in the defects above and the forth

was found during bug triage. The root cause of these failures can be

traced back to two issues: Inconsistent test condition setup and error handling.

All four defect manifestations are fixed by this set of changes.

 

 

New code built and test executed via JPRT test job; Linux ARM and
Linux PPC version built, but not tested because ARM and PPC are
currently build-only platforms in JPRT.
 

As always, comments and questions are welcome.

 

Ron

 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/attachments/20130311/7c570116/attachment-0001.html