From 21ed2a6e29611df6332e575770c35eb837f9afc7 Mon Sep 17 00:00:00 2001
From: Matt Morehouse <mascasa@google.com>
Date: Thu, 22 Feb 2018 19:00:17 +0000
Subject: [PATCH] [libFuzzer] Include TEMP_MAX_LEN in Fuzzer::PrintStats.

Reviewers: kcc

Reviewed By: kcc

Subscribers: llvm-commits

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

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@325817 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/LibFuzzer.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/LibFuzzer.rst b/docs/LibFuzzer.rst
index 7a105e5ed12..b546dec4be7 100644
--- a/docs/LibFuzzer.rst
+++ b/docs/LibFuzzer.rst
@@ -369,14 +369,16 @@ possible event codes are:
 Each output line also reports the following statistics (when non-zero):
 
 ``cov:``
-  Total number of code blocks or edges covered by the executing the current
-  corpus.
+  Total number of code blocks or edges covered by executing the current corpus.
 ``ft:``
   libFuzzer uses different signals to evaluate the code coverage:
   edge coverage, edge counters, value profiles, indirect caller/callee pairs, etc.
   These signals combined are called *features* (`ft:`).
 ``corp:``
   Number of entries in the current in-memory test corpus and its size in bytes.
+``lim:``
+  Current limit on the length of new entries in the corpus.  Increases over time
+  until the max length (``-max_len``) is reached.
 ``exec/s:``
   Number of fuzzer iterations per second.
 ``rss:``
-- 
GitLab