-
Notifications
You must be signed in to change notification settings - Fork 26
[FUZZ] Beaconfuzz_v2 crash-8aca1b5ce295f678fb67bd5ea8bb36c13a0d7f20 in struct_proposer_slashing #82
Comments
For analysis, here is a package with:
issue_82_proposer_slashing.zip FYI,
You can reproduce with:
|
This to me looks like a duplicate of #74 , which was resolved in this PR. I'm not sure if the latest version of the pfuzz library was updated accordingly. @pventuzelo can you please rebuild the libraries and push an updated version? I suspect the one currently on |
@zedt3ster correct, with the new pfuzz lib everything is correct. thanks again @Daft-Wullie |
I just got this crash again with the same filename.i am on commit a990138 and i can reproduce it reliably.
|
@Daft-Wullie Can you open a new issue with just your comment inside (it's just to keep trace and split since it's not the same affected client). Look like the same file is triggering an issue with teku this time @zedt3ster |
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-proposer_slashing-struct
Crasher file name: crash-8aca1b5ce295f678fb67bd5ea8bb36c13a0d7f20
crash-8aca1b5ce295f678fb67bd5ea8bb36c13a0d7f20.zip
Beaconstate to reproduce: a8d3de7f40c220fe927d3664d53e45ea.ssz
Client exercised: prysm(?)
Fuzzing engine used (if applicable): libfuzzer
Crash output and stacktrace
re run crasher file with
ETH2FUZZ_BEACONSTATE=../eth2fuzz/workspace/corpora/beaconstate cargo +nightly fuzz run struct_proposer_slashing fuzz/artifacts/struct_proposer_slashing/crash-8aca1b5ce295f678fb67bd5ea8bb36c13a0d7f20
and got
Your Environment
The text was updated successfully, but these errors were encountered: