aboutsummaryrefslogtreecommitdiffhomepage
path: root/docs
diff options
context:
space:
mode:
authorGravatar Mike Aizatsky <mike.aizatsky@gmail.com>2016-10-26 09:40:37 -0700
committerGravatar GitHub <noreply@github.com>2016-10-26 09:40:37 -0700
commitaadb17ae2b06b61ba1d7969a1bf0bbc94673185e (patch)
tree83c98aef64b330155c071da7d869107c03537e7b /docs
parent47e7c1030d8740f1f84bf2d0e8080c53a2251d61 (diff)
Create reproducing.md
Diffstat (limited to 'docs')
-rw-r--r--docs/reproducing.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/docs/reproducing.md b/docs/reproducing.md
new file mode 100644
index 00000000..7a9047d9
--- /dev/null
+++ b/docs/reproducing.md
@@ -0,0 +1,15 @@
+# Reproducing oss-fuzz issues
+
+You've been CC'ed on an oss-fuzz issue, now what? Before attempting a fix you should be able to reliably reproduce an issue.
+It is much simpler if you have Docker installed ([how?](installing_docker.md), [why?](faq.md#why-do-you-use-docker)), but
+is entirely possible to do without.
+
+## Docker-based
+
+Follow these steps:
+
+- download reproducer file
+- run `docker run -v <reproducer_file>:/testcase -t ossfuzz/<target> reproduce <fuzzer>`.
+ This will build a fuzzer (with recent target sources in the image) and will run it with reproducer input.
+- `docker run -v <local_sources>:/src/target_src -v <reproducer_file>:/testcase -t ossfuzz/<target> reproduce <fuzzer>` will build
+ fuzzer from your *local* target source. Use it to develop a fix and verify.