Fix FP memleak with outparam allocation (f'up to #12186)#5677
Merged
chrchr-github merged 1 commit intocppcheck-opensource:mainfrom Nov 19, 2023
Merged
Fix FP memleak with outparam allocation (f'up to #12186)#5677chrchr-github merged 1 commit intocppcheck-opensource:mainfrom
chrchr-github merged 1 commit intocppcheck-opensource:mainfrom
Conversation
Collaborator
I don't understand why it wouldn't be worth it. Does it cause technical problems? Or do you mean it's too much work? |
Collaborator
Author
The latter. There can e.g. be many variations of how a return value is checked. |
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.
I wonder if it is worth trying to get this right. We also have FPs when the return value is assigned to a variable, and that seems much harder to fix.