Panicked while fuzzing

[Changochen]

Panicked while fuzzing

[eqv]

That means that the forkserver wasn't started properly. Can you confirm that AFl is able to fuzz the same compiled target?

[Changochen]

I think the forkserver should be set up since it has run for 30 mins before it panicked. Both afl and afl++ are able to fuzz the same binary without error.

[eqv]

So the Fuzzer found a bunch of inputs in the first 30 minutes, but failed at that position during a running fuzzing campaign? The only option that I see is that the target crashed in some way that wasn't detected (maybe issuing a shutodwn command?), and then https://github.com/nautilus-fuzz/nautilus/blob/master/fuzzer/src/main.rs#L120 tried restarting the forkserver but wasn't able to (some lock file or something like that?). If this problem keeps reappearing you can try to place an unwrap at forksrv/src/lib.rs:95:17 and enable RUST_BACKTRACE=1 to see if that might be the case.

[Changochen]

So the Fuzzer found a bunch of inputs in the first 30 minutes, but failed at that position during a running fuzzing campaign?: Yes.

I see. I will try your suggestion. Thanks for the help!

[eqv]

Cool, if you manage to produce a reproducing test target/procedure with similar behavior (preferably in less than 30 minutes), I will gladly have a look at this issue!

[Changochen]

It seems the problem only apears once. I think this issue can be closed now. Thanks for the help again!

[eqv]

Hmm dang, if it ever reappears, please don't hesitate to reopen the issue!