diff --git a/README.md b/README.md index 4e68d0497..03fbe5ac5 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,7 @@ | [New Target Guide](docs/new_target.md) | [Reproducing](docs/reproducing.md) | [Targets List](targets/README.md) +| [Issue tracker](https://bugs.chromium.org/p/oss-fuzz/issues/list) [Create New Issue](https://github.com/google/oss-fuzz/issues/new) for questions or feedback. diff --git a/docs/reproducing.md b/docs/reproducing.md index a5a074715..81c79f20e 100644 --- a/docs/reproducing.md +++ b/docs/reproducing.md @@ -2,15 +2,50 @@ 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. - The process 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. +## Bug tracker reports. + +Bug reports in our bug tracker have the format: + +``` +Detailed report: + +Minimized Testcase (size): +``` + +Click the testcase download link to download the testcase (you may need to +login, using the same Google account that you've been CC'ed with). The "Detailed +report" link provides the full stack trace, as well as some additional details +that may be useful. + +For the following instructions, `$target` is the text after `Target: ` in the +report, and `$fuzzer` is the text after `Fuzzer binary: `. `$testcase_file` is +the path to the testcase you just downloaded. + +Note that for older reports, `Fuzzer binary:` and `Target:` may not exist. In +this case, please extract this information from the `Fuzzer:` field. This is +usually in the format `libFuzzer_$target_$fuzzer`. + ## Docker If you have docker installed, follow these steps: -- *Download testcase.* Each issue has a minimized testcase link. Download the testcase to a file. - *Reproduce from nightly sources:*