Lines Matching +full:asan +full:- +full:ubsan +full:- +full:regression

1 ---
6 permalink: /advanced-topics/ideal-integration/
7 ---
9 # Ideal integration with OSS-Fuzz
13 implement and maintain fuzz targets or integrate them with OSS-Fuzz in the same
19 [example](https://github.com/google/oss-fuzz/tree/master/projects/example/my-api-repo)
22 - TOC
24 ---
28 Every [fuzz target](http://libfuzzer.info/#fuzz-target):
29 * Is [maintained by code owners](#fuzz-target) in their RCS (Git, SVN, etc).
30 * Is [built with the rest of the tests](#build-support) - no bit rot! 
31 * Has a [seed corpus](#seed-corpus) with good [code coverage](#coverage).
33 * Is [continuously tested on the seed corpus](#regression-testing) with
34   [ASan/UBSan/MSan](https://github.com/google/sanitizers).
39 The code of the [fuzz target(s)](http://libfuzzer.info/#fuzz-target) should be
50 target](https://github.com/google/fuzzing/blob/master/docs/good-fuzz-target.md).
52 The interface between the [fuzz target]((http://libfuzzer.info/#fuzz-target))
69 Many different build systems exist in the open-source world. The less OSS-Fuzz
72 An ideal build integration for OSS-Fuzz looks like this:
77 …ING_ENGINE` (env var [provided]({{ site.baseurl }}/getting-started/new-project-guide/) by OSS-Fuzz…
87 This minimizes OSS-Fuzz-specific configuration, making your fuzzing more robust.
101 For better OSS-Fuzz integration,  the seed corpus should be available in
109 [nss](https://github.com/mozilla/nss-fuzzing-corpus) (corpus in a separate repo).
125 [fuzzer stats]({{ site.baseurl }}/further-reading/clusterfuzz#fuzzer-stats)
127 }}/further-reading/clusterfuzz#coverage-reports).
130 [code coverage]({{ site.baseurl }}/advanced-topics/code-coverage) page.
133 corpora, and fixing timeouts/out-of-memory bugs in your targets.
135 ## Regression Testing
138 the project's regression testing process. One way to do so is to link the fuzz
140 ([example](https://github.com/llvm-mirror/compiler-rt/tree/master/lib/fuzzer/standalone))
143 [sanitizers](https://github.com/google/sanitizers) during regression testing.
146 [openssl](https://github.com/openssl/openssl/blob/master/fuzz/test-corpus.c).
153 }}/further-reading/clusterfuzz/#performance-analyzer) for each fuzz target that
162 In such cases, we can host the fuzz targets, dictionaries, etc. in OSS-Fuzz's 
166 Examples: [libxml2](https://github.com/google/oss-fuzz/tree/master/projects/libxml2),
167 [c-ares](https://github.com/google/oss-fuzz/tree/master/projects/c-ares), [expat](https://github.co…
170 bugs found by OSS-Fuzz.