On 19 February 2010 09:38, erik quanstrom <quans...@labs.coraid.com> wrote: >> There is no mechanism which directly translates bit flips >> to crashes! The bad case is actually a corruption which >> does *not* cause a crash, but is written to disk. How
> indirection? executable code being turned into illegal > instructions? it's not 100% efficiency but it will translate > flipped bits into crashes. I believe Dave was implying that there is no mechanism that _guarantees_ that a bit flip anywhere in memory will result in a code crash. Some bit flips just might mean the wrong colour pixel on your screen, others might mean that someone's pay scale goes from $7.50 an hour to $4096 + $17.50 an hour, some might just be in an unused chunk of RAM. Flips in code are more likely to cause crashes, but still not guaranteed. > - erik -- Adrian
