PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3296
*** shadow/3296 Tue Aug 28 06:23:14 2001
--- shadow/3296.tmp.1250 Fri Sep 7 16:46:31 2001
***************
*** 32,35 ****
If a Java program takes a segmentation fault, then you have a problem in either
the JVM, the JVM's supplied libraries, a JNI routine or your physical memory,
since there should be no way Java can produce a bad pointer when operating
! corectly. And since I don't believe we're using JNIs anywhere in Xalan...
--- 32,57 ----
If a Java program takes a segmentation fault, then you have a problem in either
the JVM, the JVM's supplied libraries, a JNI routine or your physical memory,
since there should be no way Java can produce a bad pointer when operating
! corectly. And since I don't believe we're using JNIs anywhere in Xalan...
!
! ------- Additional Comments From [EMAIL PROTECTED] 2001-09-07 16:46 -------
! This could be related to the known problem described at:
!
! http://java.sun.com/j2se/1.3/install-linux-sdk.html
!
! <quote>
! The newer glibc-2.2.x libraries cannot correctly handle initial thread stack
! sizes larger than 6 MB. This can cause a segmentation fault on come Linux
! platforms that use the newer libraries. Such platforms include Red Hat 7.0,
! SuSe 7.2, and Debian 2.2. The problem will not occur on Linux platforms that
! are using glibc-2.1.x such as Red Hat 6.1 and 6.2. It will also not affect Red
! Hat 7.1 because it uses a different thread stack layout. This problem is being
! tracked as bug 4466587.
!
! Workaround - Use "ulimit -s 2048" in bash shell or "limit stacksize 2048" in
! tcsh to limit the initial thread stack to 2 MB.
! </quote>
!
! This worked for me on Mandrake 8.0.
!
!
