simplereader: Fix warning about use of pointer variable after free()#288
Merged
thiagomacieira merged 1 commit intointel:mainfrom Feb 5, 2026
Conversation
georgen117
approved these changes
Feb 5, 2026
We weren't dereferencing the variable, so this should have been safe. However, it isn't clear in the C and C++ standards whether it legitimately was safe. So let's just fix it. ``` simplereader.c:180:9: warning: pointer ‘buf’ may be used after ‘free’ [-Wuse-after-free] simplereader.c:177:5: note: call to ‘free’ here ``` Signed-off-by: Thiago Macieira <thiago.macieira@intel.com>
thiagomacieira
force-pushed
the
simplereader_Fix_warning_about_use_of_pointer_variable_after_free_
branch
from
3964a0f to
b72e830
Compare
thiagomacieira
deleted the
simplereader_Fix_warning_about_use_of_pointer_variable_after_free_
branch
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
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.
We weren't dereferencing the variable, so this should have been safe. However, it isn't clear in the C and C++ standards whether it legitimately was safe. So let's just fix it.