WIP: Opcode tracing #18
Draft
Conversation
This file contains 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
Instead of generating bit per file + line + opcode, generate bits as previously, but hash opcodes between others. Previously similar check produced same bit, different counts. Now every combination produces different bits.
Two with simple char cmp and two with strcmp.
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.
Implemented opcode tracing.
This version updates hash until we do something else. So my tests/target.py generates different maps. Without this feature same ops generate just increased count and I felt it was not enough.
You can test this with suite of: '0' '\0' 'zero' 'zero\n' and compare
This is tested with python 3.9 and afl-fuzz++ 3.00a. You need separate patch to support afl-fuzz++.
I tries to implement #15