diff options
| author | Dongliang Mu <mudongliangabcd@gmail.com> | 2019-02-26 05:02:19 -0500 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2019-02-26 11:02:19 +0100 |
| commit | a36ecd98b86f513b76b0ff71fe345292ac458c08 (patch) | |
| tree | 100f0fc2dfb424f80a53455656fdf833c4b83a7f /docs | |
| parent | 8022bafd2dabfc45e5b1850f3a8cc1950b0e59a6 (diff) | |
docs: fix one typo
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/usage.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/usage.md b/docs/usage.md index 308c8583f..a15aa1e78 100644 --- a/docs/usage.md +++ b/docs/usage.md @@ -17,7 +17,7 @@ Once syzkaller detected a kernel crash in one of the VMs, it will automatically By default it will use 4 VMs to reproduce the crash and then minimize the program that caused it. This may stop the fuzzing, since all of the VMs might be busy reproducing detected crashes. -The process of reproducing one crash may take from a few minutes up to an hour depending on whether the crash is easily reproducible or reproducible at all. +The process of reproducing one crash may take from a few minutes up to an hour depending on whether the crash is easily reproducible or non-reproducible at all. Since this process is not perfect, there's a way to try to manually reproduce the crash, as described [here](reproducing_crashes.md). If a reproducer is successfully found, it can be generated in one of the two forms: syzkaller program or C program. |