Chuck I am aware.
A SIGSEGV is a signal sent by the kernel. Not a violation itsself.
A sigsegv is sent when an invalid memory access is attempted by a
process in userspace, in other words a page fault occurs, when the page
is actually present in physical memory but cannot be accessed by the
for some reason I keep calling you chuck... I hope I'm not offending
anyone :O
On Fri, 2010-02-26 at 13:55 +0100, Taylan Develioglu wrote:
Chuck I am aware.
A SIGSEGV is a signal sent by the kernel. Not a violation itsself.
A sigsegv is sent when an invalid memory access is attempted by a
Taylan Develioglu wrote:
for some reason I keep calling you chuck... I hope I'm not offending
anyone :O
We all do that from time to time.
It comes from the fact that we know he (Chuck) is always watching us
from the sidelines, to catch anyone who doesn't know his Servlet Specs
from his
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taylan,
On 2/24/2010 8:31 AM, Taylan Develioglu wrote:
We have also had failures with hotspot error files (hs_err) present, and
the cause specified was indeed SIGSEGV indicating a page fault. But I
don't know if the two are related.
Just to be
