Avoid broken stack at few places #7353
Merged
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
catap
changed the title
|
@microsoft-github-policy-service agree |
catap
force-pushed
the
nlsat-solver-stack
branch
5 times, most recently
from
13319ec
to
3656a26
Compare
NikolajBjorner
added a commit
that referenced
this pull request
Aug 26, 2024
Signed-off-by: Nikolaj Bjorner <nbjorner@microsoft.com>
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.
Here a similar fixes which I had discovered in the codebase. All of them follow the pattern: an object is allocated on the stack, but stored as pointer. As result an access to it may lead to crash, or write into it brokes the stack.