Skip to content

Make fuzzer easier to use#5

Merged
Ollrogge merged 1 commit into
mainfrom
dev
Nov 4, 2025
Merged

Make fuzzer easier to use#5
Ollrogge merged 1 commit into
mainfrom
dev

Conversation

@Ollrogge

@Ollrogge Ollrogge commented Nov 4, 2025

Copy link
Copy Markdown
Collaborator

Main idea is to remove the need for people to create their own harness_fuzz.go and harness_test.go and having to deal with compiling the fuzzer and the coverage binary independently. Approaches work the as follows:

For fuzzing
Copy harness_fuzz.go into the harness directory passed by the user, compile fuzzer, remove harness_fuzz.go. This is implemented in build.rs.

Obtaining coverage
Copy harness_test.go into harness directory, run the test passing in the output directory of the fuzzer, remove harness_test.go from directory. This has been added as an additional command to main.rs.

The coverage file is not optimal since we can not grep for the specific project the user wants to fuzz and therefore it shows the coverage in all dependencies, so also the Go standard libraries.

@Ollrogge
Ollrogge merged commit 32cca55 into main Nov 4, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant