diff options
| author | Max Moroz <mmoroz@chromium.org> | 2019-12-12 08:52:07 -0800 |
|---|---|---|
| committer | Max Moroz <mmoroz@chromium.org> | 2019-12-12 11:09:40 -0800 |
| commit | 926fa4088cc2d6fdcd9301e80d05d9310009b660 (patch) | |
| tree | e09146d1a8d0468bbe678f8d58da8c789e8e10bc /compiler-rt/lib/fuzzer | |
| parent | bcae3a77afd171604d117393d8cb92dfca2da8bb (diff) | |
| download | bcm5719-llvm-926fa4088cc2d6fdcd9301e80d05d9310009b660.tar.gz bcm5719-llvm-926fa4088cc2d6fdcd9301e80d05d9310009b660.zip | |
[compiler-rt] libFuzzer: update -merge_control_file= help message.
Summary:
The motivation for this change is to have a distinguisher in libFuzzer
that would let the runner know whether multistep merge is supported or not by
a particular fuzz target binary. Otherwise, multistep merge fails to execute
with older version of libFuzzer, and there is no way to verify that easily.
Reviewers: kcc
Subscribers: dberris, #sanitizers, llvm-commits
Tags: #sanitizers, #llvm
Differential Revision: https://reviews.llvm.org/D71423
Diffstat (limited to 'compiler-rt/lib/fuzzer')
| -rw-r--r-- | compiler-rt/lib/fuzzer/FuzzerFlags.def | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/compiler-rt/lib/fuzzer/FuzzerFlags.def b/compiler-rt/lib/fuzzer/FuzzerFlags.def index 0e19a9cde6c..a6741574303 100644 --- a/compiler-rt/lib/fuzzer/FuzzerFlags.def +++ b/compiler-rt/lib/fuzzer/FuzzerFlags.def @@ -56,7 +56,8 @@ FUZZER_FLAG_STRING(merge_control_file, "Specify a control file used for the merge process. " "If a merge process gets killed it tries to leave this file " "in a state suitable for resuming the merge. " - "By default a temporary file will be used.") + "By default a temporary file will be used." + "The same file can be used for multistep merge process.") FUZZER_FLAG_INT(minimize_crash, 0, "If 1, minimizes the provided" " crash input. Use with -runs=N or -max_total_time=N to limit " "the number attempts." |
