Repository navigation
Fix #14990: FP memleak with function call through function pointer #8813
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
aadanen
wants to merge
10
commits into
cppcheck-opensource:main
Choose a base branch
from
aadanen:fptr_leak
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
6cd44e8
impl and tests
aadanen 64b20cd
formatting
aadanen dd3c8fd
formatting
aadanen c1593be
sanitizer
aadanen effada4
make functionCall not segfault
aadanen 1f99cf0
(int) is not lambda call
aadanen 72a9b13
fixed infinite loops on certain inputs
aadanen 4f3a25d
fixed redundantNextPrevious
aadanen 6e5b86b
clarified checks and fixed test
aadanen 1970878
format
aadanen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an AI review take it with a grain of salt. Please feel free to reject it by clicking on Resolve button
I built this branch and its merge-base, and found a new false positive when the argument of the anonymous call deallocates the resource:
The merge-base gives no warning for either function. It looks like the argument tokens are processed twice: once as the normal
fclose(f)call, and then again byfunctionCall(nullptr, lpar, ...), which seesfafter the dealloc. Could you add these as test cases?The other shapes I tried gave no new warnings:
(*cb)(p); free(p);,(cb)(NULL); free(p);,if ((*cb)(1)) { free(p); return; },(free)(p);,(*cb)(1) + (free(p), 0),(*cb)(1), fclose(f);.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My change didn't introduce a new false positive, but brought the behavior of function pointer calls into line with the current behavior of normal function calls.
the code above throws the false positive deallocuse on main.
This seems to me like it should be a separate pull request and bug report because it isn't really part of fixing the #14990 FP memleak. I understand if that fix needs to land first before we merge this one, but I don't currently have the cycles to look into it.