Rooba
/
oss-fuzz
mirror of https://github.com/google/oss-fuzz.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated ideal_integration.md (#4011)

This commit is contained in:
Shivam7-1 2020-06-19 20:17:00 +05:30 committed by GitHub
parent de5c5e69c3
commit 058247f3d3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/advanced-topics/ideal_integration.md
View File

@ -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