-
Notifications
You must be signed in to change notification settings - Fork 407
Update libFuzzer fuzz instructions #3705
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
Update libFuzzer fuzz instructions #3705
Conversation
I've assigned @valentinewallace as a reviewer! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3705 +/- ##
==========================================
+ Coverage 88.55% 89.11% +0.56%
==========================================
Files 149 155 +6
Lines 114470 121678 +7208
Branches 114470 121678 +7208
==========================================
+ Hits 101365 108430 +7065
+ Misses 10606 10584 -22
- Partials 2499 2664 +165 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
@@ -61,6 +61,7 @@ To run fuzzing using `cargo-fuzz / libFuzzer`, run | |||
|
|||
```shell | |||
rustup install nightly # Note: libFuzzer requires a nightly version of rust. | |||
export RUSTFLAGS="--cfg=fuzzing --cfg=secp256k1_fuzz --cfg=hashes_fuzz" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran into this as well, but it seems I don't need to add --cfg=fuzzing
. Does it work for you without that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cargo fuzz
should add cfg=fuzzing
automatically for us, but it also doesn't really hurt for us to add it manually. Its also required when running cargo test
in the fuzz
crate, so IMO its fine to have it be explicit.
Gonna go ahead and land this since there's little reason to nitpick over a redundant cfg. |
Without this flag , following the usual routine generates this error
Output
After introducing this , normal fuzz operation is observed