Re:Radiation-hardened quine
by dllthomas on Friday February 21, 2014 @10:19AM
(#7277310)
Fascinating exercise. "Deleting one character" seems a phenomenally unlikely outcome of radiation, though.
[ Parent
| on HN ]
Re:Radiation-hardened quine
by fnordfnordfnord on Friday February 21, 2014 @11:31AM
(#7277697)
Granted it's not "deleting" a character but here, if you haven't seen it: https://blogs.oracle.com/ksplice/entry/attack_of_the_cosmic_...
That seems to be a flipped bit, by far the most likely kind of problem due to radiation.
A harder task might be "Randomly delete, add or mutate a single character".
We had a few similar tasks on CGSE, e.g.
Addition and deletion anywhere but the end seems overwhelmingly unlikely.
Depends on how the code is stored in memory ... with ropes addition or deletion anywhere could happen.
True! But:
1) it's still less likely - most of the data is almost certainly characters of content, not sizes;
2) it's unlikely to be robust against flipped bits in pointers in the rope structures (even if implemented as indexes);
and 3) there is no reason to expect it to be limited to one byte (if an addition or deletion happens, "more than one byte" is far more likely than "one byte").
Re:Radiation-hardened quine
by TrainedMonkey on Friday February 21, 2014 @01:49PM
(#7278602)
I agree, flipping random bit is more likely. I.E. mutating random character into some other random character (does not have to be printable one). This also has a pretty strong assumption that Ruby itself is not corrupted.
Corrupting one bit is likely but if the rest of your system is not radiation hardened it isn't very helpful.