From e16e2c9a4cb6937323e861b646792a6c4c978a3c Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Tue, 4 Jun 2024 12:55:41 +0200 Subject: executor: add runner mode Move all syz-fuzzer logic into syz-executor and remove syz-fuzzer. Also restore syz-runtest functionality in the manager. Update #4917 (sets most signal handlers to SIG_IGN) --- docs/troubleshooting.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/troubleshooting.md') diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 7b1d77b51..930adbc04 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -3,11 +3,11 @@ Here are some things to check if there are problems running syzkaller. - Use the `-debug` command line option to make syzkaller print all possible debug output, - from both the `syz-manager` top-level program and the `syz-fuzzer` instances. With this option - syzkaller will only run one VM instance. + from both the `syz-manager` top-level program and the `syz-executor` instances. + With this option syzkaller will only run one VM instance. - Use the `-vv N` command line option to increase the amount of logging output, from both - the `syz-manager` top-level program and the `syz-fuzzer` instances (which go to the + the `syz-manager` top-level program and the `syz-executor` instances (which go to the output files in the `crashes` subdirectory of the working directory). Higher values of N give more output. -- cgit mrf-deployment