From e0d84b80ddefcd2f8aeb6e3d6d0e44d517116463 Mon Sep 17 00:00:00 2001 From: Abhishek Arya Date: Tue, 3 Jan 2017 11:02:33 -0800 Subject: [PATCH] Update reproducing.md --- docs/reproducing.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/reproducing.md b/docs/reproducing.md index 7189b7671..9c3172475 100644 --- a/docs/reproducing.md +++ b/docs/reproducing.md @@ -14,11 +14,11 @@ 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, all you do is run: 
-./fuzz_target_binary 
+./fuzz_target_binary <testcase_path>
-If this is a timeout bug, add the -timeout=25 argument. -If this is a OOM bug, add the -rss_limit_mb=2048 argument. +If this is a timeout bug, add the -timeout=25 argument.
+If this is an OOM bug, add the -rss_limit_mb=2048 argument.
Read more on how timeouts and OOMs are handed [here](faq.md#how-do-you-handle-timeouts-and-ooms). Depending on the nature of the bug, the fuzz target binary needs to be built with the appropriate [sanitizer](https://github.com/google/sanitizers) @@ -31,7 +31,7 @@ to replicate the exact build steps used by OSS-Fuzz and then feed the reproducer - *Reproduce using latest OSS-Fuzz build:* 
-python infra/helper.py reproduce $PROJECT_NAME  
+   python infra/helper.py reproduce $PROJECT_NAME <fuzzer_name> <testcase_path>
It builds the fuzzer from the most recent successful OSS-Fuzz build (usually last night's sources) @@ -45,8 +45,8 @@ python infra/helper.py reproduce libxml2 libxml2_xml_read_memory_fuzzer ~/Downlo - *Reproduce using local source checkout:* 
-python infra/helper.py build_fuzzers $PROJECT_NAME 
-python infra/helper.py reproduce $PROJECT_NAME  
+python infra/helper.py build_fuzzers $PROJECT_NAME <source_path>
+python infra/helper.py reproduce $PROJECT_NAME <fuzzer_name> <testcase_path>
This is essentially the previous command that additionally mounts local sources into the running container.