Cppcheck analysis limit.

[fjpanag]

Describe the bug
I am getting lots of warnings from cppcheck: cppcheck-normalCheckLevelMaxBranches.

It prompts me to:

Limiting analysis of branches. Use --check-level=exhaustive to analyze all branches.

This is indeed an expected behavior from cppcheck, and indeed enabling --check-level=exhaustive resolves the issue (in stand-alone cppcheck).

However, as far as I can tell, it is not possible to enable this setting through CodeChecker.

Please consider enabling this option (or providing a CodeChecker option to enable the respective cppcheck option).

I spend a considerable amount of time to resolve this, but I didn't succeed. If this is already possible, please consider improving the documentation on this matter.

CodeChecker version

bash-5.2$ CodeChecker version
[INFO 2025-02-03 22:26] - CodeChecker analyzer version:
---------------------------------------------------------------
Kind                 | Version                                 
---------------------------------------------------------------
Base package version | 6.24.4                                  
Package build date   | 2024-10-28T15:46                        
Git commit ID (hash) | 454d978191ed42c8202a2244dc092dfb6fd8c83a
Git tag information  | 6.24.4                                  
---------------------------------------------------------------

[INFO 2025-02-03 22:26] - CodeChecker web version:
------------------------------------------------------------------------------
Kind                                | Version                                 
------------------------------------------------------------------------------
Base package version                | 6.24.4                                  
Package build date                  | 2024-10-28T15:46                        
Git commit ID (hash)                | 454d978191ed42c8202a2244dc092dfb6fd8c83a
Git tag information                 | 6.24.4                                  
Server supported Thrift API version | 6.58                                    
Client Thrift API version           | 6.58                                    
------------------------------------------------------------------------------

To Reproduce

Run CodeChecker, with cppcheck enabled, on a file with deep enough branches to trigger the issue.

Expected behaviour

Have a CLI option in CodeChecker to enable exhaustive analysis with cppcheck.

Desktop (please complete the following information)

• OS: Fedora 41
• Browser: Firefox

Additional context

Not sure if it is important, but this is how CodeChecker is invoked in my case:

CodeChecker analyze ./bin/code_checker/compile_commands.json --enable sensitive \
	--disable cppcheck-preprocessorErrorDirective \
	--disable bugprone-branch-clone \
	--disable bugprone-multi-level-implicit-pointer-conversion \
	--disable alpha.unix.PthreadLock \
	--disable cert-err33-c \
	--disable cert-err34-c \
	--disable clang-diagnostic-format-nonliteral \
	--ctu --skip ./test/code_checker/skipfile --output ./bin/code_checker/reports

[kali20177]

The CodeChecker analyze command supports a deprecated flag --cppcheckargs to pass arguments. You can save --check-level=exhaustive in a separate file (e.g., cppcheck.cfg) and then run:

CodeChecker analyze ./bin/code_checker/compile_commands.json \
  --cppcheckargs ./test/code_checker/cppcheck.cfg \
  --enable sensitive \
  ...  \
  --ctu --skip ./test/code_checker/skipfile --output ./bin/code_checker/reports

This might be helpful.

[dkrupp]

After version 6.25.0, there is a new way of passing verbatim parameters to the cppcheck is

CodeChecker analyze --analyzer-config cppcheck:cc-verbatim-args-file= ./cppcheck.cfg
the content of the ./cppcheck.cfg file should be
--check-level=exhaustive

[amai2012]

@dkrupp Is there way to configure this w/o creating a cppcheck.cfg file?

I am using the same script to run codechecker on various projects and would prefer to change the behaviour at a single place.

[bruntib]

@amai2012, No, there is no other way, currently. Do you have a suggestion on how to distinguish that single place in the project if using the same script?

[amai2012]

Raw CLI argument?

[bruntib]

Maybe, you could create multiple config files and choose between them by providing one or the other in the CLI. This would be similar, but instead of giving the file content to the CLI, you give a filename there. Would you think, this is a feasible solution?

[amai2012]

I am running CodeChecker from a pipeline script/file where I would prefer to use not external files.

Certainly it's possible to put them somewhere, but I wanted to make sure there is no simple approach.

[bruntib]

No, there is no such feature. Currently, only a file can be given to these flags.