On Wed, 2002-07-24 at 12:38, Mark Neidorff wrote:
> 
> Recently I've started getting a signal 15 error.  Is it bad hardware that
> would cause it?

It *might* be, but I wouldn't be too quick to jump to that conclusion. 
You can test your memory easily enough using memtest86:
http://www.memtest86.com/

Signal 15 is only a strong indication of bad memory when you are
experiencing sporadic errors in very reliable software doing the same
operations.  For instance, if gcc SEGV's while compiling a specific C
file some, but not all of the time, then that might be the effect of bad
RAM.  If, however, gcc always SEGV'd, then it's probably a bug in gcc. 
Software can SEGV for other reasons, though, mostly bugs in that
software.




_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to