diff options
| author | Max Moroz <mmoroz@chromium.org> | 2020-10-05 12:53:37 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-10-05 12:53:37 -0700 |
| commit | f8bd878191dbaf665406b6655d21ecb0b925d4b7 (patch) | |
| tree | 243206809da570a5a9154234d82f0f4dde07ef7b /docs | |
| parent | 0fe19f69cb821408afcce1d5425fbd34b4b74fb4 (diff) | |
| download | oss-fuzz-f8bd878191dbaf665406b6655d21ecb0b925d4b7.tar.gz | |
[docs] Reproducing: clarify that reproduce command works only with libfuzzer (#4497). (#4504)
The change was proposed by @pauldreik in https://github.com/google/oss-fuzz/issues/4497#issuecomment-703075579
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/advanced-topics/reproducing.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/advanced-topics/reproducing.md b/docs/advanced-topics/reproducing.md index 9b5e29732..95bb09c5c 100644 --- a/docs/advanced-topics/reproducing.md +++ b/docs/advanced-topics/reproducing.md @@ -93,6 +93,9 @@ After you build an image and a fuzzer, you can reproduce a bug by running the fo $ python infra/helper.py reproduce $PROJECT_NAME <fuzz_target_name> <testcase_path> ``` +**Note**: The reproduce command only supports `libfuzzer` fuzzing engine. Crashes +found with other fuzzing engines should be reproducible with `libfuzzer` too. + For example, to build the [libxml2](https://github.com/google/oss-fuzz/tree/master/projects/libxml2) project with UndefinedBehaviorSanitizer (`undefined`) instrumentation and reproduce a crash testcase for a fuzzer named `libxml2_xml_read_memory_fuzzer`, |