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

Update new_library.md

This commit is contained in:
Mike Aizatsky 2016-10-13 08:27:26 -07:00 committed by GitHub
parent 42959c5fd6
commit 70805aea3b
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/new_library.md
View File

@ -49,7 +49,7 @@ It is very simple for most libraries:
FROM ossfuzz/base-libfuzzer # base image with clang toolchain
MAINTAINER YOUR_EMAIL # each file should have a maintainer
RUN apt-get install -y ... # install required packages to build a project
COPY build.sh /src/ # install build script for the project.
COPY build.sh <additional_files> /src/ # install build script and other files.
```
Expat example: [expat/Dockerfile](../expat/Dockerfile)
@ -133,17 +133,19 @@ passing them manually to a build tool might be required.
### Custom libFuzzer options for ClusterFuzz
By default ClusterFuzz will run your fuzzier without any options. You can specify
options by creating a `fuzzer_name.options` file next to a fuzzier in `/out`:
By default ClusterFuzz will run your fuzzer without any options. You can specify
custom options by creating a `fuzzer_name.options` file next to a fuzzier in `/out`:
```
[linfuzzer]
max_len = 1024
```
[Available options](http://llvm.org/docs/LibFuzzer.html#options)
[List of available options](http://llvm.org/docs/LibFuzzer.html#options)
For out of tree fuzzes You will commonly add options file using docker's
At least `max_len` is highly recommended.
For out of tree fuzzers you will likely add options file using docker's
`COPY` directive and will copy it into output in build script.
### Dictionaries