From 97060c44dec9c25b8c74a4ee05a217bd68f119fe Mon Sep 17 00:00:00 2001 From: Abhishek Arya Date: Tue, 24 Sep 2019 16:25:00 -0700 Subject: [PATCH] Fix typo --- docs/further-reading/fuzzer_environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/further-reading/fuzzer_environment.md b/docs/further-reading/fuzzer_environment.md index c7cde3841..233cb25d3 100644 --- a/docs/further-reading/fuzzer_environment.md +++ b/docs/further-reading/fuzzer_environment.md @@ -45,7 +45,7 @@ to `'$ORIGIN'`, the path of the binary (see the discussion of `'$ORIGIN'` [here] A fuzzer can be instructed to load libraries relative to `'$ORIGIN'` during compilation (i.e. `-Wl,-rpath,'$ORIGIN/lib'` ) or afterwards using `chrpath -r '$ORIGIN/lib' $OUT/$fuzzerName` ([example](https://github.com/google/oss-fuzz/blob/09aa9ac556f97bd4e31928747eca0c8fed42509f/projects/php/build.sh#L40)). Note that `'$ORIGIN'` should be surronded by single quotes because it is not an environment variable like `$OUT` that can be retrieved during execution of `build.sh`. -Its value is retrieved during execution of the binary. You can very that you did this correctly using `ldd ` and the `check_build` command in helper.py. +Its value is retrieved during execution of the binary. You can verify that you did this correctly using `ldd ` and the `check_build` command in `infra/helper.py`. You should ensure that the fuzz target works correctly by using `run_fuzzer` command (see instructions