fix: cppcheck warnings in standalone/#3488
Merged
airween merged 3 commits intoowasp-modsecurity:v2/masterfrom Feb 4, 2026
Merged
fix: cppcheck warnings in standalone/#3488airween merged 3 commits intoowasp-modsecurity:v2/masterfrom
airween merged 3 commits intoowasp-modsecurity:v2/masterfrom
Conversation
|
airween
approved these changes
Feb 4, 2026
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
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.



what
cppcheckwarnings in all.c,.cppand.hfiles within thestandalonedirectory.cppcheckcommand has been connected into the workflow.why
cppcheckcould not find the necessary system and Apache headers, resulting in numerous "missing include" warnings and incorrect analysis.cppcheckon the standalone directory now produces zero warnings locally and in CI.references
cppcheckconfiguration logic inMakefile.amwas based on thev3/masterbranch.notes