diff options
author | Bruno P. Kinoshita <kinow@users.noreply.github.com> | 2021-04-21 10:46:16 +1200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-04-20 15:46:16 -0700 |
commit | d38fd0220af986edce26999a6595c97348df6a97 (patch) | |
tree | 457247a87f4d0c4f8e63b2348294bb092d61f731 /docs/further-reading | |
parent | 56e5d9b2920e5c0e09818147e8ca2c085ea3b063 (diff) | |
download | oss-fuzz-d38fd0220af986edce26999a6595c97348df6a97.tar.gz |
Fix typos and one link (#5645)
* Fix link to Jenkins
* Typos
* Fix builder, not jenkins.
Co-authored-by: Abhishek Arya <inferno@chromium.org>
Diffstat (limited to 'docs/further-reading')
-rw-r--r-- | docs/further-reading/clusterfuzz.md | 2 | ||||
-rw-r--r-- | docs/further-reading/fuzzer_environment.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/further-reading/clusterfuzz.md b/docs/further-reading/clusterfuzz.md index 92d85ff4c..308882c2d 100644 --- a/docs/further-reading/clusterfuzz.md +++ b/docs/further-reading/clusterfuzz.md @@ -46,7 +46,7 @@ information, memory usage) on our fuzzer statistics dashboard. We provide coverage reports, where we highlight the parts of source code that are being reached by your fuzz target. Make sure to look at the uncovered code -marked in red and add appropriate fuzz targets to cover those usecases. +marked in red and add appropriate fuzz targets to cover those use cases. ![coverage_1]({{ site.baseurl }}/images/freetype_coverage_1.png?raw=true) ![coverage_2]({{ site.baseurl }}/images/freetype_coverage_2.png?raw=true) diff --git a/docs/further-reading/fuzzer_environment.md b/docs/further-reading/fuzzer_environment.md index 7c527ec32..459db3429 100644 --- a/docs/further-reading/fuzzer_environment.md +++ b/docs/further-reading/fuzzer_environment.md @@ -43,7 +43,7 @@ We strongly recommend static linking because it just works. However dynamic linking can work if shared objects are included in the `$OUT` directory and are loaded relative to `'$ORIGIN'`, the path of the binary (see the discussion of `'$ORIGIN'` [here](http://man7.org/linux/man-pages/man8/ld.so.8.html)). 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 +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 surrounded 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 verify that you did this correctly using `ldd <fuzz_target_name>` and the `check_build` command in `infra/helper.py`. |