It's a stack overflow on this input: fn main () { pri&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&ntln
-
-
-
AddressSanitizer reports the error in a much saner way, but enabling it also leads to many false positives, e.g. https://github.com/rust-fuzz/cargo-fuzz/issues/87 … :(
End of conversation
New conversation -
-
-
First step: Rust defends your code Second step: Rust fights back
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The fuzzee has surpassed the fuzzer
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Isn't that how cargo-fuzz is supposed to work? There is no distinction between your code and the fuzzer, it's one instrumented program
-
So when the fuzzer detects an issue, the whole thing always exits.
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.