Polyspace Bug Finder Shows Defects Although Not Activated

When Polyspace Bug Finder (Server?) has run in our CI/CD pipeline, I get following summary in the report:

Why does Polyspace scan for so-called Defects (null pointer, division by zero, dead code etc.) even though we did not activate them in our checkers file (XML file), see:

Answer 1

[Pratyush Swain]

Hi Ismet,

I did some searching and found that Polyspace performs default defect detection such as null pointer, division by zero, and dead code, etc. regardliess of the settings in the checkers selection XML file because these defects are part of static code analysis rather than coding standard compliance checks.

You can find the list of Polyspace Bug Finder defect checkers enabled by default here: https://www.mathworks.com/help/bugfinder/ug/polyspace-bug-finder-defects-checkers-enabled-by-default.html

For modifying the default behaviour of Bug Finder checks or choosing specific bug finder defect checkers, please refer to following resosurces:

1 - https://www.mathworks.com/help/bugfinder/ug/modify-default-behavior-of-bug-finder-checkers.html

2 - https://www.mathworks.com/help/bugfinder/ug/choose-specific-defects.html

Hope this helps.

Answer 2

[Christian Bard]

Defects are not managed by the option -checkers-selection-file but with option -checkers.

Note that -chekers-activation-file allows to manage both defects and other coding Standard.