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 > 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 > program. > When this kind of violation occurs the a sigsegv is sent by the kernel > to the violating program. > > At least that's what 'Understanding the linux kernel' leads me to > believe (chapter process address space, page fault exception handler > p376 - 378). > > On Thu, 2010-02-25 at 22:36 +0100, Christopher Schultz wrote: > > -----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 clear, a SIGSEGV is a "segmentation violation" (memory read > > outside process space), not a "page fault", which is a perfectly normal > > thing to occur during execution. The latter is a virtual memory matter > > handled by the operating system and should be transparent (other than a > > delay) to the application. > > > > http://en.wikipedia.org/wiki/Segmentation_violation > > http://en.wikipedia.org/wiki/Page_fault > > > > The Wikipedia page for "Page fault" does indicate that "Invalid page > > fault" is a term that essentially means "null pointer dereference" but > > I've never heard that term used, ever. > > > > - -chris > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.10 (MingW32) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > > > iEYEARECAAYFAkuG7UMACgkQ9CaO5/Lv0PAdLgCfUypdTf332QZ6JHyTzPlS4Lu5 > > 4xMAnReYrzhvO9xiSS7qB331Tq5DwPpx > > =5cqn > > -----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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
