diff options
| author | Abhishek Arya <inferno@chromium.org> | 2020-04-07 21:29:16 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-07 21:29:16 -0700 |
| commit | 42bf235998b87cf282b117edb3e71623bb0ad899 (patch) | |
| tree | b811a03587d424afdefe4cf399820b173251d3a3 /docs | |
| parent | bc308a7a32677b839dd67c2f06539d7b42bca843 (diff) | |
| download | oss-fuzz-42bf235998b87cf282b117edb3e71623bb0ad899.tar.gz | |
Add Honggfuzz to new project guide doc.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/getting-started/new_project_guide.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/getting-started/new_project_guide.md b/docs/getting-started/new_project_guide.md index 9132254af..ea6b372a7 100644 --- a/docs/getting-started/new_project_guide.md +++ b/docs/getting-started/new_project_guide.md @@ -218,9 +218,9 @@ cp $SRC/*.dict $SRC/*.options $OUT/ If your project is written in Go, check out the [Integrating a Go project]({{ site.baseurl }}//getting-started/new-project-guide/go-lang/) page. -**Notes:** +**Note:** -1. Don't assume the fuzzing engine is libFuzzer by default, because we generate builds for both libFuzzer and AFL fuzzing engine configurations. Instead, link the fuzzing engine using $LIB_FUZZING_ENGINE. +1. Don't assume the fuzzing engine is libFuzzer by default, because we generate builds for libFuzzer, AFL and Honggfuzz fuzzing engine configurations. Instead, link the fuzzing engine using $LIB_FUZZING_ENGINE. 2. Make sure that the binary names for your [fuzz targets]({{ site.baseurl }}/reference/glossary/#fuzz-target) contain only alphanumeric characters, underscore(_) or dash(-). Otherwise, they won't run on our infrastructure. 3. Don't remove source code files. They are needed for code coverage. |