Closed Daft-Wullie closed 4 years ago
It looks like this might be an issue with the block fuzzer itself - @pventuzelo is investigating and should be able to confirm shortly.
Thanks for the report @Daft-Wullie ;)
It's an issue in the fuzzer actually, the lighthouse harness was not returning an error in certain cases. I fixed it in 3d0d06c4e5be463af6a78104ce927dce1758f102
Thanks ;)
I've done and provided the following:
[FUZZ]
issue already refers to that crasherbeacon-fuzz
version or commit used.Info to Reproduce
Command run: e.g.
make fuzz_block-struct
Crasher file name: crash-b22ce997bf58f944a6b96aff5ffb3673e3ec75c2 crash-b22ce997bf58f944a6b96aff5ffb3673e3ec75c2.zip
Client exercised: (nimbus?)
Fuzzing engine used (if applicable): libfuzzer
Crash output and stacktrace
command used to reproduce:
ETH2FUZZ_BEACONSTATE=../eth2fuzz/workspace/corpora/beaconstate cargo +nightly fuzz run struct_block fuzz/artifacts/struct_block/crash-b22ce997bf58f944a6b96aff5ffb3673e3ec75c2
Your Environment