Closed vanhauser-thc closed 11 months ago
Tried this in a random project, this is fixed by the fact we do not have a minimization-loop anymore.
Worst case scenario it runs the fuzzer against a random binary that does not take data as input, but I don't see a way of doing a good sanity-check against that.
me or bruno were in the wrong directory (/fuzz/targets/foo and not /fuzz/targets/foo/runtime/foo/fuzz) and hence cargo ziggy run build the targets but could not find them, resulting in a loop of starting afl-fuzz (fails invisible), trying minimization (fails invisible) and back to afl-fuzz etc. a check that this does not happen would be nice :)