Handle comparison of freed pointers in assertions #143
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
Until now, we only handled correct comparison of freed pointers in normal conditions, not in assertions. Note: --pointer-check must be used to handle freed pointers properly.
viktormalik
force-pushed
the
freed-ptr-fix
branch
from
44c7297 to
1e37fa7
Compare
Collaborator
Author
|
@peterschrammel this is a feature request from a student writing a paper where he performs some experiments with 2LS. It would be great if you could merge it ASAP. Thanks |
peterschrammel
approved these changes
May 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Until now, we only handled correct comparison of freed pointers in normal conditions, not in assertions.