You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As many times as you want, inject some random code that shouldn't change the meaning of the program.
Such as if false { ...deleterious side effects... } or if true { ...original statement... }.
Where false and true above could be arbitrarily complex expressions that the fuzzer knows evaluate to false and true.
The main part of the fuzzer will be a library of valid bits of code to inject.
Run the original code and the changed code.
(Optional, but nice) If a difference is detected in output/behavior, try to minimize the injected code that still reproduces such a difference.
I got the idea from this paper which does the same but with graphics shaders.
I have a fairly high confidence in Alma's runtime semantics nowadays. It's been a long time since we found an embarrassing bug in that department. Still, I suspect if we did this, we'd still drag up something, somewhere. 😄
The text was updated successfully, but these errors were encountered:
if false { ...deleterious side effects... }
orif true { ...original statement... }
.false
andtrue
above could be arbitrarily complex expressions that the fuzzer knows evaluate tofalse
andtrue
.I got the idea from this paper which does the same but with graphics shaders.
I have a fairly high confidence in Alma's runtime semantics nowadays. It's been a long time since we found an embarrassing bug in that department. Still, I suspect if we did this, we'd still drag up something, somewhere. 😄
The text was updated successfully, but these errors were encountered: