You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ViDeZZo currently enables persisting fuzzing. Testcases in input.not_interesting/ are necessary to reproduce crashes if any. The size grows very quickly, which is normal, and you need larger storage for that. Based on my experience, also depending on the target, you'd better have 1TB for 1-hour fuzzing.
This is what I recommend now. Run the fuzzing campaign without the corpus for a long time and check if there is any crash. If so, enable the corpus to reproduce the crash on a machine with large storage. This strategy is enough for our research but I know it is an open issue.
Two technical ways to fix this issue.
Enable the fork server. I was doing this but haven't finished it. I need to sync the coverage/feature from the child processes to the parent process. Then I have to fine-tune the performance issue as using a fork server is way too slow.
Develop a good way to record part of the test cases. This is a research question and I haven't had a good idea.
hello, I run ViDeZZo through the following command:
the input folder holds the initial seed
But in the same level directory, there is an
input.not_interesting
folder that grows in size very quickly when fuzzing and quickly fills up my disk.I want to know how to deal with it. Thanks.
The text was updated successfully, but these errors were encountered: