From aea2971f5ca4ec1fc725ef980501b4ca4c00a1c9 Mon Sep 17 00:00:00 2001 From: Arik Sosman Date: Fri, 10 Apr 2020 11:22:46 -0700 Subject: [PATCH] Add details on asserting latest version in the dependencies and listing targets. --- fuzz/README.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/fuzz/README.md b/fuzz/README.md index 59a4a8f3d..922579232 100644 --- a/fuzz/README.md +++ b/fuzz/README.md @@ -18,10 +18,8 @@ should be more than sufficient. To install `honggfuzz`, simply run ```shell +cargo update cargo install honggfuzz --force - -export HFUZZ_BUILD_ARGS="--features honggfuzz_fuzz" -cargo hfuzz build ``` ### Execution @@ -30,12 +28,19 @@ To run the Hongg fuzzer, do ```shell export CPU_COUNT=1 # replace as needed +export HFUZZ_BUILD_ARGS="--features honggfuzz_fuzz" export HFUZZ_RUN_ARGS="-n $CPU_COUNT --exit_upon_crash" -export TARGET="" # replace with the target to be fuzzed +export TARGET="msg_ping_target" # replace with the target to be fuzzed cargo hfuzz run $TARGET ``` +To see a list of available fuzzing targets, run: + +```shell +ls ./src/bin/ +``` + ## A fuzz test failed on Travis, what do I do? You're trying to create a PR, but need to find the underlying cause of that pesky fuzz failure blocking the merge? -- 2.39.5