forks/go-ethereum
1
0
Fork 1
mirror of https://github.com/ethereum/go-ethereum.git synced 2026-08-17 17:33:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

FIx typos README.md

Browse source
This commit is contained in:
Soulcollector 2025-01-04 22:10:27 +03:00 committed by GitHub
parent 20b95cd55b
commit c7e58487c8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
tests/fuzzers/README.md
View file

@ -31,11 +31,10 @@ go-fuzz -bin ./rlp/rlp-fuzz.zip
### Notes
Once a 'crasher' is found, the fuzzer tries to avoid reporting the same vector twice, so stores the fault in the `suppressions` folder. Thus, if you
e.g. make changes to fix a bug, you should _remove_ all data from the `suppressions`-folder, to verify that the issue is indeed resolved.
Once a 'crasher' is found, the fuzzer tries to avoid reporting the same vector twice, so it stores the fault in the `suppressions` folder. Thus, if you, for example, make changes to fix a bug, you should _remove_ all data from the `suppressions`-folder, to verify that the issue is indeed resolved.
Also, if you have only one and the same exit-point for multiple different types of test, the suppression can make the fuzzer hide different types of errors. So make
sure that each type of failure is unique (for an example, see the rlp fuzzer, where a counter `i` is used to differentiate between failures:
Also, if you have only one and the same exit point for multiple different types of test, the suppression can make the fuzzer hide different types of errors. So make
sure that each type of failure is unique (for example, see the RLP fuzzer, where a counter `i` is used to differentiate between failures:
```golang
if !bytes.Equal(input, output) {