New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add a description for fuzzer output columns #248
Comments
Yes, we should document these in the readme. I actually think we shouldn’t display restarts at all, but instead monitor them and print a warning on stderr as needed; the warning could explain the problem more fully. |
I agree restarts is not very useful as is. |
For myself I would be happy with any reasonable, and rough, description of coverage. It doesn't need to be a percentage value. But since it isn't it would be nice to have an idea of what this ever increasing number actually is. |
There are two columns whose meaning are unclear to me.
Cover - this is not a percent value, so a description would help to interpret this.
Restarts - it’s unclear to me what causes the fuzzer to restart. There is an indication that you should aim to restart 1/1000 but it’s not clear how to influence this.
The text was updated successfully, but these errors were encountered: