TIL that some fuzzers use code coverage metrics to drive their strategies. That's really clever! If some input can hit a line that was not previously being executed, chances are variations on it may hit more lines that haven't been covered yet.
-
-
Isn't this something rust-analyzer is meant to be good at?
-
I think it's a bit different. RA only does static analysis of Rust code — parses, links, borrow checks, etc. Miri is a full-blown interpreter. It runs Rust code in a VM and can instrument it as it's being executed. Which seems excellent to check coverage and mess with the AST.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.