commit 38279cb015f46a88b9e299c1cf4b0fd1ccd12f16
author dor1s <dor1s> Tue Sep 12 02:01:54 2017 +0000
committer dor1s <dor1s> Tue Sep 12 02:01:54 2017 +0000
tree 2366cf5144fc97a29f301b88e9f811ca21133461
parent 3dff99e117e97cc49a1168c7c3ad513782e8a816

[libfuzzer] Compare TotalNumberOfRuns with MaxNumberOfRuns when testing a memory leak.

Summary:
Fuzzer::TryDetectingAMemoryLeak may call ExecuteCallback which would
increment TotalNumberOfRuns, but it doesn't respect Options.MaxNumberOfRuns
value specified by a user.

Context: https://github.com/google/oss-fuzz/issues/822#issuecomment-328153970

Reviewers: kcc

Reviewed By: kcc

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

git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk/lib/fuzzer@312993 91177308-0d34-0410-b5e6-96231b3b80d8

FuzzerLoop.cpp

diff --git a/FuzzerLoop.cpp b/FuzzerLoop.cpp
index 0354fc8..d6185fd 100644
--- a/FuzzerLoop.cpp
+++ b/FuzzerLoop.cpp
@@ -525,6 +525,8 @@
                                      bool DuringInitialCorpusExecution) {
   if (!HasMoreMallocsThanFrees) return;  // mallocs==frees, a leak is unlikely.
   if (!Options.DetectLeaks) return;
+  if (!DuringInitialCorpusExecution &&
+      TotalNumberOfRuns >= Options.MaxNumberOfRuns) return;
   if (!&(EF->__lsan_enable) || !&(EF->__lsan_disable) ||
       !(EF->__lsan_do_recoverable_leak_check))
     return;  // No lsan.