This is an archive of the discontinued LLVM Phabricator instance.

Differential D139284

Fix LibFuzzer documentation (timeout exit code)
Needs ReviewPublic

Authored by Porges on Dec 4 2022, 6:17 PM.

Details

Reviewers
kcc
Summary

The current documentation claims that timeout and internal error default to the same exit code (77). This is incorrect; timeouts default to 70.

Diff Detail

Revision Contents

PathSize
llvm/
docs/
LibFuzzer.rst
LibFuzzer.rst
2 lines

Diff 479957

llvm/docs/LibFuzzer.rst

Show First 20 Lines • Show All 275 Lines • ▼ Show 20 Lines``-rss_limit_mb``
the process is treated as a failure case. the process is treated as a failure case.
The limit is checked in a separate thread every second. The limit is checked in a separate thread every second.
If running w/o ASAN/MSAN, you may use 'ulimit -v' instead. If running w/o ASAN/MSAN, you may use 'ulimit -v' instead.
``-malloc_limit_mb`` ``-malloc_limit_mb``
If non-zero, the fuzzer will exit if the target tries to allocate this If non-zero, the fuzzer will exit if the target tries to allocate this
number of Mb with one malloc call. number of Mb with one malloc call.
If zero (default) same limit as rss_limit_mb is applied. If zero (default) same limit as rss_limit_mb is applied.
``-timeout_exitcode`` ``-timeout_exitcode``
Exit code (default 77) used if libFuzzer reports a timeout. Exit code (default 70) used if libFuzzer reports a timeout.
``-error_exitcode`` ``-error_exitcode``
Exit code (default 77) used if libFuzzer itself (not a sanitizer) reports a bug (leak, OOM, etc). Exit code (default 77) used if libFuzzer itself (not a sanitizer) reports a bug (leak, OOM, etc).
``-max_total_time`` ``-max_total_time``
If positive, indicates the maximum total time in seconds to run the fuzzer. If positive, indicates the maximum total time in seconds to run the fuzzer.
If 0 (the default), run indefinitely. If 0 (the default), run indefinitely.
``-merge`` ``-merge``
If set to 1, any corpus inputs from the 2nd, 3rd etc. corpus directories If set to 1, any corpus inputs from the 2nd, 3rd etc. corpus directories
that trigger new code coverage will be merged into the first corpus that trigger new code coverage will be merged into the first corpus
▲ Show 20 Lines • Show All 563 Lines • Show Last 20 Lines