mirror of https://github.com/google/oss-fuzz.git
Update ideal_integration.md
This commit is contained in:
parent
69359d9612
commit
bf627d4507
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue