reactos/syzkaller
1
0
Fork 0
mirror of https://github.com/reactos/syzkaller.git synced 2025-03-03 00:59:13 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: fix one typo

Browse Source
This commit is contained in:
Dongliang Mu 2019-02-26 05:02:19 -05:00 committed by Dmitry Vyukov
parent 8022bafd2d
commit a36ecd98b8
1 changed files with 1 additions and 1 deletions

2
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.