[llvm] r263331 - [libFuzzer] refresh docs more

[Kostya Serebryany via llvm-commits]

Author: kcc
Date: Fri Mar 11 21:11:27 2016
New Revision: 263331

URL: http://llvm.org/viewvc/llvm-project?rev=263331&view=rev
Log:
[libFuzzer] refresh docs more

Modified:
    llvm/trunk/docs/LibFuzzer.rst

Modified: llvm/trunk/docs/LibFuzzer.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/LibFuzzer.rst?rev=263331&r1=263330&r2=263331&view=diff
==============================================================================
--- llvm/trunk/docs/LibFuzzer.rst (original)
+++ llvm/trunk/docs/LibFuzzer.rst Fri Mar 11 21:11:27 2016
@@ -342,7 +342,7 @@ you will want to know whether the functi
 One easy to use metric is, of course, code coverage.
 You can get the coverage for your corpus like this::
 
-  ASAN_OPTIONS=coverage_pcs=1 ./fuzzer CORPUS_DIR -runs=0
+  ASAN_OPTIONS=coverage=1 ./fuzzer CORPUS_DIR -runs=0
 
 This will run all the tests in the CORPUS_DIR but will not generate any new tests
 and dump covered PCs to disk before exiting.
@@ -371,9 +371,6 @@ the program arguments that you can read
     return 0;
    }
 
-Finally, you may use your own ``main()`` and call ``FuzzerDriver``
-from there, see FuzzerInterface.h_.
-
 Try to avoid initialization inside the target function itself as
 it will skew the coverage data. Don't do this::