Hi, On Fri, Nov 12, 2010 at 12:55:23AM -0800, Eninja wrote: > Either way, I'd hate to bust your bubble and this is the last time I'll say > this, SegV exceptions in IOS are always caused by software bugs.
You don't seem to understand anything about hardware failure modes.
If you have a bad RAM that will change a pointer value for you *without*
triggering a RAM parity error (because it's on a platform that has no
ECC/parity, like 'early 7200 NPEs'), and the software uses that pointer,
and accesses a bad memory location *because the RAM corrupted the pointer*,
how can the resulting SegV be "always a software bug"?
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
pgpmsAgfpoLnT.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
