In order to avoid issues during a minimization that happens during a fuzzing run, the output/shared_corpus is moved to a directory called output/main_corpus, and the output of the minimization is set to output/shared_corpus/.
This creates an issue when the fuzzer is stopped in the middle of minimization: the shared corpus has changed directory, and the user needs to manually move it back to where it should be.
Fixing this issue could involve either:
using output/shared_corpus as the input for minimization (which had caused issues in the past, but we need to try it again)
moving the directory on ctrl+c, before exiting
displaying a message to the user, instructing them how to handle the situation
I think we should first try the first option, and use one of the others if it fails.
In order to avoid issues during a minimization that happens during a fuzzing run, the
output/shared_corpusis moved to a directory calledoutput/main_corpus, and the output of the minimization is set tooutput/shared_corpus/.This creates an issue when the fuzzer is stopped in the middle of minimization: the shared corpus has changed directory, and the user needs to manually move it back to where it should be.
Fixing this issue could involve either:
output/shared_corpusas the input for minimization (which had caused issues in the past, but we need to try it again)I think we should first try the first option, and use one of the others if it fails.