From bf627d45077224ffb39a865a0181998ad1b8db37 Mon Sep 17 00:00:00 2001 From: Oliver Chang Date: Mon, 24 Apr 2017 19:24:00 -0700 Subject: [PATCH] Update ideal_integration.md --- docs/ideal_integration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/ideal_integration.md b/docs/ideal_integration.md index d64bdfb4b..ec2f0fc1a 100644 --- a/docs/ideal_integration.md +++ b/docs/ideal_integration.md @@ -91,15 +91,15 @@ Ideally, a dictionary should be maintained alongside the fuzz target. The syntax is described [here](http://libfuzzer.info/#dictionaries). ## Coverage -For a fuzzer to be useful, it must have good coverage in the code that it is testing. You can view the coverage +For a fuzz target to be useful, it must have good coverage in the code that it is testing. You can view the coverage for your fuzz targets by looking at the [fuzzer stats](https://github.com/google/oss-fuzz/blob/master/docs/clusterfuzz.md#fuzzer-stats) dashboard on ClusterFuzz, as well as [coverage reports](https://github.com/google/oss-fuzz/blob/master/docs/clusterfuzz.md#coverage-reports). Coverage can often be improved by adding dictionaries, more inputs for the seed corpora, and fixing timeouts/out-of-memory bugs in your targets. -## Fuzzer performance -Fuzzers should also be performant, as high memory usage and/or slow execution speed can slow the down +## Performance +Fuzz targets should also be performant, as high memory usage and/or slow execution speed can slow the down the growth of coverage and finding of new bugs. ClusterFuzz provides a (performance analyzer)[https://github.com/google/oss-fuzz/blob/master/docs/clusterfuzz.md] for each fuzz target that shows problems that are impacting the performance of the fuzz target.