aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorDongliang Mu <mudongliangabcd@gmail.com>2020-05-19 10:03:20 -0400
committerDmitry Vyukov <dvyukov@google.com>2020-05-19 16:22:52 +0200
commit5d11c3ecfdbb8ee069ef3e56b31af6ff224ed55f (patch)
treefc00761999c99ab9656a054ca74113e0fab110a8 /docs
parent6d882fd26c01d118a584b2a3aecd5f08fa5e11e1 (diff)
docs: add the link of manager config file used in the syz-repro
Diffstat (limited to 'docs')
-rw-r--r--docs/reproducing_crashes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/reproducing_crashes.md b/docs/reproducing_crashes.md
index 28759f627..679e6ba88 100644
--- a/docs/reproducing_crashes.md
+++ b/docs/reproducing_crashes.md
@@ -17,7 +17,7 @@ Now, run `syz-prog2c` tool on the program. It will give you executable C source.
If the crash is not reproducible with `-threaded/collide=0` flags, then you need this last step. You can think of threaded/collide mode as if each syscall is executed in its own thread. To mode such execution mode, move individual syscalls into separate threads. You can see an example here: https://groups.google.com/d/msg/syzkaller/fHZ42YrQM-Y/Z4Xf-BbUDgAJ.
-This process is automated to some degree in the `syz-repro` utility. You need to give it your manager config and a crash report file:
+This process is automated to some degree in the `syz-repro` utility. You need to give it your manager config and a crash report file. And you can refer to the [example config file](/pkg/mgrconfig/testdata/qemu.cfg).
```
./syz-repro -config my.cfg crash-qemu-1-1455745459265726910
```