commit ffef3b73d49feb71787d018e7dda9c8f30999d3a
author Max Moroz <mmoroz@chromium.org> Wed May 23 19:42:30 2018 +0000
committer Copybara-Service <copybara-worker@google.com> Thu Mar 25 23:17:04 2021 -0700
tree 90bf31879c6ddc68118c460ebbaa8a5658ef4a9e
parent 0579c6c93980335e5eb4a4aed20bce94b56d4c11

[libFuzzer] Don't complain about lack of interesting inputs when -runs=0.

Summary:
The most common usecase for -runs=0 is for generating code coverage
over some corpus. Coverage reports based on sancov are about to be deprecated,
which means some external coverage solution will be used, e.g. Clang source
based code coverage, which does not use any sancov instrumentations and thus
libFuzzer would consider any input to be not interesting in that case.

Reviewers: kcc

Reviewed By: kcc

Subscribers: alex, delcypher, #sanitizers, llvm-commits

Differential Revision: https://reviews.llvm.org/D47271

llvm-svn: 333116
GitOrigin-RevId: fe97441c2c61f6cbd0104f299540d7ddf4f068b0

FuzzerLoop.cpp

diff --git a/FuzzerLoop.cpp b/FuzzerLoop.cpp
index d5b949c..9c19ba9 100644
--- a/FuzzerLoop.cpp
+++ b/FuzzerLoop.cpp
@@ -743,7 +743,7 @@
     Printf("INFO: %zd/%zd inputs touch the focus function\n",
            Corpus.NumInputsThatTouchFocusFunction(), Corpus.size());
 
-  if (Corpus.empty()) {
+  if (Corpus.empty() && Options.MaxNumberOfRuns) {
     Printf("ERROR: no interesting inputs were found. "
            "Is the code instrumented for coverage? Exiting.\n");
     exit(1);