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

Update reproducing.md

This commit is contained in:
Abhishek Arya 2017-01-05 23:34:57 -08:00 committed by GitHub
parent 355c87f736
commit e4da5a4bca
1 changed files with 16 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/reproducing.md
View File

@ -13,9 +13,9 @@ This file contains the bytes that were fed to the [Fuzz Target](http://libfuzzer
If you have already [integrated](ideal_integration.md) the fuzz target with your build and test system, If you have already [integrated](ideal_integration.md) the fuzz target with your build and test system,
all you do is run: all you do is run:
<pre> ```bash
./fuzz_target_binary <b><i>&lt;testcase_path&gt;</i></b> $ ./fuzz_target_binary <testcase_path>
</pre> ```
If this is a timeout bug, add the <b><i>-timeout=25</i></b> argument.<br /> If this is a timeout bug, add the <b><i>-timeout=25</i></b> argument.<br />
If this is an OOM bug, add the <b><i>-rss_limit_mb=2048</i></b> argument.<br /> If this is an OOM bug, add the <b><i>-rss_limit_mb=2048</i></b> argument.<br />
@ -30,24 +30,25 @@ to replicate the exact build steps used by OSS-Fuzz and then feed the reproducer
- *Reproduce using latest OSS-Fuzz build:* - *Reproduce using latest OSS-Fuzz build:*
<pre> ```bash
python infra/helper.py reproduce <b><i>$PROJECT_NAME</i></b> <b><i>&lt;fuzzer_name&gt;</i></b> <b><i>&lt;testcase_path&gt;</i></b> $ python infra/helper.py reproduce $PROJECT_NAME <fuzzer_name> <testcase_path>
</pre> ```
It builds the fuzzer from the most recent successful OSS-Fuzz build (usually last night's sources) It builds the fuzzer from the most recent successful OSS-Fuzz build (usually last night's sources)
and feeds the testcase file to the target function. and feeds the testcase file to the target function.
E.g. for [libxml2](../projects/libxml2) project with fuzzer named `libxml2_xml_read_memory_fuzzer`, it will be: E.g. for [libxml2](../projects/libxml2) project with fuzzer named `libxml2_xml_read_memory_fuzzer`, it will be:
<pre> ```bash
python infra/helper.py reproduce libxml2 libxml2_xml_read_memory_fuzzer ~/Downloads/testcase $ python infra/helper.py reproduce libxml2 libxml2_xml_read_memory_fuzzer ~/Downloads/testcase
</pre> ```
- *Reproduce using local source checkout:* - *Reproduce using local source checkout:*
<pre> ```bash
python infra/helper.py build_fuzzers <b><i>$PROJECT_NAME</i></b> <b><i>&lt;source_path&gt;</i></b> $ python infra/helper.py build_fuzzers $PROJECT_NAME <source_path>
python infra/helper.py reproduce <b><i>$PROJECT_NAME</i></b> <b><i>&lt;fuzzer_name&gt;</i></b> <b><i>&lt;testcase_path&gt;</i></b> $ python infra/helper.py reproduce $PROJECT_NAME <fuzzer_name> <testcase_path>
</pre> ```
This is essentially the previous command that additionally mounts local sources into the running container. This is essentially the previous command that additionally mounts local sources into the running container.
- *Fix issue*. Write a patch to fix the issue in your local checkout and then use the previous command to verify the fix (i.e. no crash occurred). - *Fix issue*. Write a patch to fix the issue in your local checkout and then use the previous command to verify the fix (i.e. no crash occurred).