Chris and Andre,
Andre's note that it was always code that was not meant for the platform
triggered a thought that it might be remnants of the jre Slackware includes
in their distribution. Let me explain. I have been installing Slackware
by just saying 'load everything'. Then, I would remove the jre 'package'
using the package manager. My thought was what if the package manager is
not removing everything? So, I am rebuilding one of the servers eliminating
unwanted packages before they are installed (take less than 30 minutes...
not certain how I can get a 10 minute test to see if I accomplished
anything.)
I agree with Chris that the only definitive way of finding the problem is to
get a stack trace. It seems to me we have two stack traces that we need to
know about: 1) the jvm stack trace and 2) the java stack trace. Running gdb
against the core dump only tells me the problem was in the jvm because there
is no debugging info in the jvm. So, the only way to get the details would
seem to be to build the jvm from source (I have downloaded the source but
haven't built the jvm yet.) I don't know how to force a java stack dump at
point of failure, not even certain it is possible because it would seem the
the failure in the C code in the jvm would mean the jvm would stop before it
could give a stack trace.
Understand that this is my best guess and that this area is removed from my
usual mundane Java application development. If anyone has suggestions, I am
open to them because I know I know very little.
Thanks,
Carl
----- Original Message -----
From: "Christopher Schultz" <ch...@christopherschultz.net>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Saturday, February 13, 2010 9:46 AM
Subject: Re: Tomcat dies suddenly
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
André,
On 2/12/2010 7:29 PM, André Warnier wrote:
I would just like to mention that in 90% of the cases where I have seen
a Seg Fault, it was due to the attempted execution of a piece of binary
code not meant for the current platform.
(It's been a while since I've seen one though.)
In a Java context, for me it's always been either misbehaving native
code (/not/ from Sun... this would be "application" code), or bad
hardware. Maybe another run through memtest86+ would be a good idea.
I'd love to see a stack trace from a few crashes, though.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkt2u18ACgkQ9CaO5/Lv0PBGsQCgvhnXtIby1uP47o3BmjN8Hlyh
USAAn1P/xLbv3tDhsTto6lWXDfwd4lM7
=xovn
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
