mirror of
https://github.com/reactos/syzkaller.git
synced 2025-02-07 20:38:52 +00:00
docs: fix a typo and improve formatting (#1031)
This commit is contained in:
parent
5de92d341e
commit
7c693b5241
@ -13,9 +13,9 @@ Once you have a single program that causes the crash, try to minimize it by remo
|
||||
|
||||
Now that you have a minimized program, check if the crash still reproduces with `./syz-execprog -threaded=0 -collide=0` flags. If not, then you will need to do some additional work later.
|
||||
|
||||
Now, run `syz-prog2c` tool on the program. It will give you executable C source. If the crash reproduces with -threaded/collide=0 flags, then this C program should cause the crash as well.
|
||||
Now, run `syz-prog2c` tool on the program. It will give you executable C source. If the crash reproduces with `-threaded/collide=0` flags, then this C program should cause the crash as well.
|
||||
|
||||
If the crash id 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.
|
||||
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:
|
||||
```
|
||||
|
Loading…
x
Reference in New Issue
Block a user