diff options
| author | Shivam7-1 <55046031+Shivam7-1@users.noreply.github.com> | 2020-06-19 20:17:00 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-19 07:47:00 -0700 |
| commit | 058247f3d3aa2441c6342b7a4cc9325297b52a95 (patch) | |
| tree | 6177470475157b5f6e8d64c4c5f5a441050c7ab8 /docs | |
| parent | de5c5e69c3ea9b008475a1bcea8d662e6135cab7 (diff) | |
| download | oss-fuzz-058247f3d3aa2441c6342b7a4cc9325297b52a95.tar.gz | |
Updated ideal_integration.md (#4011)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/advanced-topics/ideal_integration.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/advanced-topics/ideal_integration.md b/docs/advanced-topics/ideal_integration.md index b83fafe6d..7e1865307 100644 --- a/docs/advanced-topics/ideal_integration.md +++ b/docs/advanced-topics/ideal_integration.md @@ -73,7 +73,7 @@ An ideal build integration for OSS-Fuzz looks like this: * For every fuzz target `foo` in the project, there is a build rule that builds `foo_fuzzer`, a binary that: * Contains the fuzzing entry point. - * Contains (`LLVMFuzzerTestOneInput`) and all the code it depends on + * Contains (`LLVMFuzzerTestOneInput`) and all the code it depends on. * Uses the `main()` function from `$LIB_FUZZING_ENGINE` (env var [provided]({{ site.baseurl }}/getting-started/new-project-guide/) by OSS-Fuzz environment). * Since the build system supports changing the compiler and passing extra compiler flags, the build command for `foo_fuzzer` looks similar to this: @@ -143,7 +143,7 @@ in previous step. We recommend you use [sanitizers](https://github.com/google/sanitizers) during regression testing. Examples: [SQLite](https://www.sqlite.org/src/artifact/d9f1a6f43e7bab45), -[openssl](https://github.com/openssl/openssl/blob/master/fuzz/test-corpus.c) +[openssl](https://github.com/openssl/openssl/blob/master/fuzz/test-corpus.c). ## Performance |