Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Main idea is to remove the need for people to create their own
harness_fuzz.goandharness_test.goand having to deal with compiling the fuzzer and the coverage binary independently. Approaches work the as follows:For fuzzing
Copy
harness_fuzz.gointo the harness directory passed by the user, compile fuzzer, removeharness_fuzz.go. This is implemented inbuild.rs.Obtaining coverage
Copy
harness_test.gointo harness directory, run the test passing in the output directory of the fuzzer, removeharness_test.gofrom directory. This has been added as an additional command tomain.rs.The coverage file is not optimal since we can not
grepfor the specific project the user wants to fuzz and therefore it shows the coverage in all dependencies, so also the Go standard libraries.