dereference null pointer directly in crash command #1501
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
`test[123]` would result in `*(test+123)`, which may point to valid memory that we modify. Instead dereference the null pointer directly to ensure we actually crash
Jan200101
commented
May 21, 2023
Comment on lines
773
to
-774
| uint8_t* test = nullptr; | ||
| test[123] = 5; |
There was a problem hiding this comment.
Going a bit further, this could be improved by making it volatile, since the compiler may decide that this is nonsense and to ignore it.
abort() may even be better, but that results in a different reror.
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.
test[123]would result in*(test+123), which may point to valid memory that we modify. Instead dereference the null pointer directly to ensure we actually crash