Red Hat Bugzilla – Bug 124366
Sun's java JDK's segfault on an athlon 64
Last modified: 2015-01-04 17:06:26 EST
Description of problem:
Using either the stable 32bit Java 1.4.2 sdk or the beta 1.5.0 64 bit one from
http://java.sun.com, I get segfaults when trying to run Jakarta-tomcat-4.1.30 from
Steps to Reproduce:
1. set JAVA_HOME to where the SDK live.
2. turn on coredumps with ulimit -c 10000000
3. cd jakarta-tomcat-4.13
5. access a webapp via your browser.
6. look at the segfaults (via dmesg) or core file
The machine passed a round of memtest86 testing.
I can send in more info upon request.
oops, the above should read "cd jakarta-tomcat-4.1.30", not 4.13.
I haven't tried the blackdown or IBM JDK's yet, but I will.
I've also tried LD_ASSUME_KERNEL=2.4.19 and 2.2.5
one more detail, the processes segfault with signal 6 SIGABRT.
the fix for this (turned out to be a false message) is in the most
recent bk kernels (post 2.6.7-rc3 I believe).
It might be a good idea to include it in a future update release as it
avoids user confusion.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.