Fix FP leakNoVarFunctionCall with Qt object#4272
Merged
orbitcowboy merged 12 commits intocppcheck-opensource:mainfrom Jul 13, 2022
Merged
Fix FP leakNoVarFunctionCall with Qt object#4272orbitcowboy merged 12 commits intocppcheck-opensource:mainfrom
orbitcowboy merged 12 commits intocppcheck-opensource:mainfrom
Conversation
Collaborator
Author
|
Seems like |
Collaborator
It requires the |
Collaborator
Author
Yeah, I'm trying to work around that now... |
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
3 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.
Although
connect()was missing leak-ignore, the FP came up since windows.cfg also has aconnect().The warning for HelpDialog looks like a true positive to me.