diff options
| author |  Evgeny Vereshchagin <evvers@ya.ru> | 2022-03-21 08:46:42 +0300 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2022-03-21 16:46:42 +1100 |
| commit | 189c961dc6162118f98bacd6164175e9206e5936 (patch) | |
| tree | 163c51b794d16264ef7665098fe689e64d962a01 /docs | |
| parent | d237f777a799820f54a1a0cb180b6aec9c238fdb (diff) | |
docs: drop out-of-date paragraph (#7403)
Issues like https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45628
aren't always reproducible with libFuzzer so to really trigger them using
the OSS-Fuzz toolchain they should be built and run with engines used to
trigger them originally. `reproduce` supports them now.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/advanced-topics/reproducing.md | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/docs/advanced-topics/reproducing.md b/docs/advanced-topics/reproducing.md index 99d5f2ac..d65fedce 100644 --- a/docs/advanced-topics/reproducing.md +++ b/docs/advanced-topics/reproducing.md @@ -105,9 +105,6 @@ 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`, |