tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jake" <j...@marinar.com>
Subject Re: SIGSEGV 11 (*) segmentation violation
Date Wed, 06 Sep 2000 01:07:03 GMT
Mark,

SIGSEGV 11 is a memory issue. Run a memory checker - chances are you have a
piece of bad ram.

--Jake
----- Original Message -----
From: Craig R. McClanahan <Craig.McClanahan@eng.sun.com>
To: <tomcat-user@jakarta.apache.org>
Sent: Tuesday, September 05, 2000 8:17 PM
Subject: Re: SIGSEGV 11 (*) segmentation violation


> mark@smartmonsters.com wrote:
>
> > [snip]
>
> > 2. For me the SIGSEGV 11 crashes didn't happen with Tomcat 3.1.  Only
> > started when I upgraded to 3.2b2.  Same VM, it was the Tomcat version
> > which changed.
> >
>
> All that means is that whatever is triggering the VM to crash wasn't
> encountered with 3.1, and was with 3.2 -- not that there was no bug
> present.
>
> There are *zero* ways that any pure-Java program (such as Tomcat) can
> legitimately cause a JVM to segfault -- using native code is something
> else again, but isn't an issue here.  Such problems are *always* due to
> a bug in the VM itself.
>
> > --Mark
> >
>
> Craig McClanahan
>
> ====================
> See you at ApacheCon Europe <http://www.apachecon.com>!
> Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
> Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
>                                     Applications to Tomcat
>


Mime
View raw message