• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1# Troubleshooting
2
3Here are some things to check if there are problems running syzkaller.
4
5 - Use the `-debug` command line option to make syzkaller print all possible debug output,
6   from both the `syz-manager` top-level program and the `syz-fuzzer` instances. With this option
7   syzkaller will only run one VM instance.
8
9 - Use the `-v N` command line option to increase the amount of logging output, from both
10   the `syz-manager` top-level program and the `syz-fuzzer` instances (which go to the
11   output files in the `crashes` subdirectory of the working directory). Higher values of
12   N give more output.
13
14 - If logging indicates problems with the executor program (e.g. `executor failure`),
15   try manually running a short sequence of system calls:
16     - Copy `syz-executor` and `syz-execprog` into a running VM.
17     - In the VM run `./syz-execprog -executor ./syz-executor -debug sampleprog` where
18       sampleprog is a simple system call script (e.g. just containing `getpid()`).
19     - For example, if this reports that `clone` has failed, this probably indicates
20       that the test kernel does not include support for all of the required namespaces.
21       In this case, running the `syz-execprog` test with the `-sandbox=setuid` option fixes the problem,
22       so the main configuration needs to be updated to set `sandbox` to `setuid`.
23
24Also see [this](linux/troubleshooting.md) for Linux kernel specific troubleshooting advice.
25
26If none of the above helps, file a bug on [the bug tracker](https://github.com/google/syzkaller/issues)
27or ask us directly on the syzkaller@googlegroups.com mailing list.
28Please include syzkaller commit id that you use and `syz-manager` output with `-debug` flag enabled if applicable.
29