From e30da1edc773f3e7e828dd4d89f34b9302939821 Mon Sep 17 00:00:00 2001 From: inferno-chromium Date: Wed, 30 Nov 2016 16:37:55 -0800 Subject: [PATCH] Update reproducing.md --- docs/reproducing.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reproducing.md b/docs/reproducing.md index 31bb7fc6d..1dfb10115 100644 --- a/docs/reproducing.md +++ b/docs/reproducing.md @@ -13,7 +13,7 @@ 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 $testcase_file
+./fuzz_target_binary $testcase_file_absolute_path
 
Depending on the nature of the bug, the fuzz target binary needs to be built with the appropriate [sanitizer](https://github.com/google/sanitizers) (e.g. if this is a buffer overflow, with [AddressSanitizer](http://clang.llvm.org/docs/AddressSanitizer.html)). @@ -25,7 +25,7 @@ to replicate the exact build steps used by OSS-Fuzz and then feed the reproducer - *Reproduce using latest OSS-Fuzz build:*
-docker run --rm -ti -v $testcase_file:/testcase ossfuzz/$project reproduce $fuzzer
+docker run --rm -ti -v $testcase_file_absolute_path:/testcase ossfuzz/$project reproduce $fuzzer
    
It builds the fuzzer from the most recent successful OSS-Fuzz build (usually last night's sources) @@ -40,7 +40,7 @@ docker run --rm -ti -v ~/Downloads/testcase:/testcase ossfuzz/<
     docker run --rm -ti -v $local_source_checkout_dir:/src/$project \
-                        -v $testcase_file:/testcase ossfuzz/$project reproduce $fuzzer
+                        -v $testcase_file_absolute_path:/testcase ossfuzz/$project reproduce $fuzzer
     
This is essentially the previous command that additionally mounts local sources into the running container.