"Thalia L. Hooker" wrote:
>
> remet@stripped:
>
> Are you only getting signal 11 from mysql? If you are getting sig11
> elsewhere, IIRC, it might be related to your memory chips. I think
> there is a faq on the net about signal 11. Several years ago I kept
> getting signal 11 when recompiling a kernel and it was due to a bad
> memory chip. The sofware tests available on the net couldn't detect
> the bad chip. But I took it out, and had the RAM checked out with a
> more expensive tester [CompUSA] and it was indeed bad.
>
> Doesn't hurt to try checking... although it could be way off base.
>
> Thalia
Signal 11 ( SIGSEGV) is caused by referencing an address that is outside of the
memory space of the process. 95% or so of the time this is caused by a bug in
the program that does not make sure a pointer points to something valid, and
tries to follow it ( Thou shalt not follow a NULL pointer! ). An hardware error
could theorectically cause segfault, for example, a bit error in RAM could
corrupt a memory reference, or the same could happen if I/O problem corrupts the
executable or the data, but this is not as common as software bugs.
--
Sasha Pachev
+------------------------------------------------------------------+
| TcX ____ __ _____ _____ ___ == mysql@stripped |
| /*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sasha Pachev |
| /*/ /*/ /*/ \*\_ |*| |*||*| mailto:sasha@stripped |
| /*/ /*/ /*/\*\/*/ \*\|*| |*||*| Provo, Utah, USA |
| /*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____ |
| ^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^ |
| /*/ \*\ Developers Team |
+------------------------------------------------------------------+
