4 tests fail for 131_10 b1 VM testing on SuSe 8.2 personal.
They cause a segmentation fault.
 (tests pass with 1.4.2)
No regression present with the 131 JDK.
Tests also fail on the java desktop OS, madhatter. (built on SuSe)
tests fail on earlier releases of jdk131_x also.
These tests pass on  customer  linux.

UNEXPECTED FAILURES:
jit/jit_suite/overflow
misc/jit_tests/overflow
misc/jit_tests/t099
misc/jit_tests/t100


       
twirl root.Linux.i386/t099# /usr/java/jdk1.3.1_03/bin/java -Xcomp -classpath /root/JQA/ts131/VM/root.Linux.i386/t099 t099
Segmentation fault
twirl root.Linux.i386/t099# /usr/java/jdk1.3.1_10/bin/java -Xcomp -classpath /root/JQA/ts131/VM/root.Linux.i386/t099 t099
Segmentation fault
twirl root.Linux.i386/t099# /usr/java/j2sdk1.4.2_02/bin/java -Xcomp -classpath /root/JQA/ts131/VM/root.Linux.i386/t099 t099
java.lang.StackOverflowError detected, thrown, and caught.
twirl root.Linux.i386/t099# 

log files attached.
hotpot.log file included for one testcase :
root.Linux.i386/overflow/hotspot.log

  xxxxx@xxxxx   2003-09-19

N/A

----------------------------------------
  xxxxx@xxxxx   2004-02-18


The bug is due to insufficient stack overflow checking from java code where stack overflow exception can be caught and handled correctly.
Here the VM / native code would run into the yellow zone.

This issue and other simialr issues were rectified in matis for c1, c2 and the interpreter using a stack "shadow" region of distance to bang ahead on the stack. The bug# which fixed it in mantis is 4697667(it consolidates fixes for realed bugs as well). 
webrev is at --
file:///net/philli.east/files/coleenp/webrev/stack_overflow/index.html
/net/jano.sfbay/export/disk05/hotspot/auto/ar/baseline/20021016-155830/putbacks

For some additional modifications see 
/net/jano/export/disk05/hotspot/auto/ar/baseline/20021027-104022/putbacks as well.

----------------------------------------------------------

This bug is reproducible in 1.4.0, and 1.4.1 too. The fix in 1.4.2 requires extensive changes as indicated by the webrevs above.

The changes are probably too exensive to backport and there have been several additional changes (before and after) to the code that would make this level of a change quite risky for an update release.

Some of these stack overflow tests are not representative of what a real user would do, and expose holes in our implementation that a real use would never notice.

This bug is not to be backported into 1.3.1 update releases.


  xxxxx@xxxxx   2004-02-26