The 99.999% was poetic license and my figure - however the point is that from what I've seen and read most are hardware caused. As one of the sources says - if you're using software that is debugged or in wide usage (as Gentoo, gcc, etc. is) it's probably hardware. I've seen overheating cause it, bad motherboards, and of course bad memory. If you're developing software and testing it then yes, you can have problems.

When you say fixed memory problems - do you mean replaced physical memory or corrected a program problem with errant pointers, etc.?

On Mon, 9 Jun 2003 13:07:28 -0700
 Josh Helmer <[EMAIL PROTECTED]> wrote:
On Monday 09 June 2003 09:22 am, brett holcomb wrote:
Just because Windows doesn't seg fault doesn't mean it's
not broken. The compling, etc. we do with Gentoo is far
harder on a system then Windows. In addition Windows may
not tell you - it just gives some strange error.


99.999% of seg faults are hardware. There is a definitive
reference on this but I don't have it where I can get to
it.

Whoa!!! I suspect that your source is horribly mistaken! I *might* believe that 99% of SIGBUS errors are caused by hardware, but I have seen literally thousands of SIGSEGV dumps, and to the best of my knowledge every one of them was caused by software problems. In fact, I *know* that many of them were because I have fixed more than a few of the memory problems that caused the SIGSEGV in the first place...


Josh


-- [EMAIL PROTECTED] mailing list



--
[EMAIL PROTECTED] mailing list



Reply via email to