-
Notifications
You must be signed in to change notification settings - Fork 40
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
Large fuzz target fails due to _HF_PC_GAURD_MAX being too small #19
Comments
Hi @adam-rhebo, |
We can probably change it for everybody, is 32Mo guards sufficient for your tests? |
For now |
Unsure, it's probably large enough already that CPU caching doesn't matter much at this point, so maybe not. |
Please try at HEAD or with google/honggfuzz@e2be7a9 |
Works like a charm and I am seeing no significant reduction fuzzing speed. Thank you very much for your swift help! |
That's great! I'll pull that and issue a new release asap 🙂 |
Our CI fuzzing recently broke as our fuzz target became too large so that honggfuzz would fail with errors like
This process has too many PC guards
. It seems this is based on a hard-coded constant_HF_PC_GUARD_MAX
in thehonggfuzz.h
header which can only be changed when honggfuzz is built.Hence, for now I resorted to adding
to this crate's build script.
Would this be something you would accept upstream (controlled via an environment variable by the Cargo
hfuzz
subcommand)? Do you have any other ideas how to avoid this problem? Thank you for your help!The text was updated successfully, but these errors were encountered: