Store log fix and more 2 #23
Open
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
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.
Building on top of the last pull request:
Store-Log with cases of store width
Raise error on rollback's failure
Seed non-speculative errors into corpus (error traceability)
Fixed segmentation-fault problem in store-log.
Added some comments.
The additional sudo(s) might be inadequate for the master version.
Indirect jump pointer corruption might have an unwanted effect on the analysis report.
The problem occurs when the corrupted target is an arbitrary address within the executable.
(eg. un-instrumented code or the middle of an instruction)