Draft
Conversation
d24b48f to
a8b8bee
Compare
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.
Your checklist for this pull request
Detailed description
This is finally an extension of LAVA's features. The objective is to pick a project, compile it, and generate new inputs utilizing concolic execution and KLEE's random path searching. This is picking up where #76 left off, although it was decided best to focus on tech debt fixing first before adding the new inputs.
The objective of this PR is to use random new inputs that extend code coverage to plant bugs in harder-to-find locations.
...
Test plan
I don't think this is worth adding to CI/CD; perhaps a quick test confirming that code coverage has expanded? Not exactly the best test idea.
However, by the time this PR is ready for merging, this will have been tested in all binaries used in the Chaff Bug paper and any new ones in the upcoming LAVA upgraded paper.
Ideally, we should store the inputs to re-test this when we get this working on ARM for the second paper.
...
Closing issues
N/A
...