When running the JCK14 runtime tests on SuSE 8.2 with 1.4.1_06b01 two of the tests fail:
vm/concepts/exceptions/exceptions031/exceptions03101
vm/concepts/exceptions/exceptions031/exceptions03102

uname -a:
Linux twirl 2.4.20-4GB #1 Mon Mar 17 17:54:44 UTC 2003 i686 unknown unknown GNU/Linux

Running through JCK doesn't give much information in the jtr files (files are attached). Just says unexpected exit code 129, but if you run the test manually it shows a segmentation fault.

A similar bug was logged before on SuSE 7.1 (4530230) but turned out to be the wrong kernel. Don't think it's the case here.

To Reproduce, run the following script (setting your JAVA_HOME path correctly):

#!/bin/sh
JAVA_HOME=/export/home/jdks/j2sdk1.4.1_06
JCK=/net/latte.ireland/export/home4/jck/JCK-runtime-14
export CLASSPATH="$JCK/classes:$JCK/javatest.jar"

$JAVA_HOME/bin/java -Xfuture -showversion javasoft.sqe.tests.vm.concepts.exceptions.exceptions031.exceptions03101.exceptions03101
$JAVA_HOME/bin/java -Xfuture -showversion javasoft.sqe.tests.vm.concepts.exceptions.exceptions031.exceptions03102.exceptions03102

 xxxxx@xxxxx  2003-11-17

Try this workaround as root:

    echo 0 > /proc/sys/vm/heap-stack-gap

Verify if this solve the problem.


 xxxxx@xxxxx  2003-11-18

I've tried this workaround and the 2 tests pass with it.

 xxxxx@xxxxx  2003-11-11

Investigate this issue. 1.4.1_XX is never qualified with 8.2.
As per QA 1.5 does not exhibit the said behaviour.

Is problem reproducible with 1.4.2_XX ?

 xxxxx@xxxxx  2003-11-11

Since 1.4.1_XX was never qualified on SuSE 8.2 and moreover since 1.4.1_XX
will EOL in January, JWSSE believes that possibility of any bug exposure is
little. As such this bug may be treated as not to be show-stopper for 
1.4.1_06/07.

I will speak to Darin Rieck, program manager for update releases for final
word on this and decide whether we need to investigate this bug.

 xxxxx@xxxxx  2003-11-12

Darin Rieck Program manager agrees that this should not be considered a 
stopper for 1.4.1_XX as we are EOL's 1.4.1_XX shortly. JWSSE will not be investigating this issue. QA can remove this from their stopper list.

 xxxxx@xxxxx  2003-11-17

Behaviour seen may be similar to what was fixed in 1.4.2 as a fix of
4821821.

QA needs to verify the work-around provided and see if the test results
are as expected.