You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-53
Original file line number
Diff line number
Diff line change
@@ -65,59 +65,6 @@ You can also always find the full command-line options that are available with
65
65
$ cargo fuzz --help
66
66
```
67
67
68
-
## Code coverage
69
-
70
-
### Prerequisites
71
-
Install the LLVM-coverage tools as described in the [Unstable book](https://doc.rust-lang.org/beta/unstable-book/compiler-flags/source-based-code-coverage.html#installing-llvm-coverage-tools).
72
-
73
-
We recommend using at least LLVM 11 and a recent nightly version of the Rust toolchain.
74
-
This code was tested with `1.51.0-nightly (2021-02-10)`.
75
-
76
-
### Generate code-coverage data
77
-
78
-
After you fuzzed your program, use the `coverage` command to generate precise
- compiles your project using the `-Zinstrument-coverage` Rust compiler flag,
87
-
- runs the program _without fuzzing_ on the provided corpus (if no corpus directory is provided it uses `fuzz/corpus/<target>` by default),
88
-
- for each input file in the corpus, generates raw coverage data in the `fuzz/coverage/<target>/raw` subdirectory,
89
-
- merges the raw files into a `coverage.profdata` file located in the `fuzz/coverage/<target>` subdirectory.
90
-
91
-
Use the generated `coverage.profdata` file to generate coverage reports and visualize code-coverage information
92
-
as described in the [Unstable book](https://doc.rust-lang.org/beta/unstable-book/compiler-flags/source-based-code-coverage.html#creating-coverage-reports).
93
-
94
-
### Example
95
-
96
-
Suppose we have a `compiler` fuzz target for which we want to visualize code coverage.
0 commit comments