----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Stan Hughes:
In my experience, these happen for only one of two reasons. Either you
have accessed an array past its boundries, or, you have written to the
NULL segment by using a null pointer as a target operand for an
assignment... The latter is harder to do in java...
Of course, I'm fairly new to java so my experience of 12 years of C,
C++, Fortran and others may not be applicable...
Your right Stan, it is not applicable. Actually neither of the things you
mention
will cause that in java. Accessing an array past its boundries generates
a java.lang.IndexOutOfBoundsException and trying to use a null pointer
generates a java.lang.NullPointerException both of which are just treated
from then on like any other Exception.
In general from my experience your JVM dies for one of the following reasons:
- the JVM has a bug, misconfiguration or OS conflict none of which your code
has much effect on.
- you are using native code (via JNI) that is doing the things you mention
above.
I have once written a small java application that would crash the HP JVM
consistently,
and run just fine on Suns JVMS. This was a bug in the HP JVM and has since
been fixed.
regards,
Johan Philippe
E&Y Consulting
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
