Stefano Bonicatti
03/19/2020, 5:16 PMTo provide a corpus for my_fuzzer, put my_fuzzer_seed_corpus.zip file next to the fuzz target's binary in $OUT during the build. Individual files in this archive will be used as starting inputs for mutations. The name of each file in the corpus is the sha1 checksum (which you can get using the sha1sum or shasum comand) of its contents.
Specifically the last sentence. Although it's weird that it says "is" instead of "must be", our files inside the .zip are not named with the sha1 of the content.. could it be this that makes it not pick up the files?
And last but not least, how we were testing our scripts/implementation on their environment, without having to merge into master?