cppcheck/addons
Sebastian 8a32a210f8
addons: Change shebang to use Python 3 instead of Python 2 (#2361)
Use Python 3 instead of Python 2 if addons are executed directly.
Running cert.py and misra.py against test/cfg/std.c.dump shows that
Python 3 needs only half the time compared to Python 2. I have tested
it repeatedly and the results are always the same. This is no surprise
at all. The memory footprint is very likely also significantly better
but i have not tested it.
2019-11-15 21:38:20 +01:00
..
doc Addons: Add README (#2047) 2019-07-28 07:51:03 +02:00
test misra.py: Add regression test for R21.1 crash (#2356) 2019-11-13 20:36:31 +01:00
README.md addons: fixup image in README (#2277) 2019-10-17 07:08:10 +02:00
ROS_naming.json Feature/ros naming check (#1511) 2019-01-09 18:16:51 +01:00
__init__.py misra.py: Fix up and improve load rules parser. (#1895) 2019-06-17 21:17:29 +02:00
cert.py addons: Change shebang to use Python 3 instead of Python 2 (#2361) 2019-11-15 21:38:20 +01:00
cppcheckdata.doxyfile Fix some typos in comments (found by codespell) 2016-11-27 11:40:42 +01:00
cppcheckdata.py addons: Clean up and clarify addons usage. (#2359) 2019-11-15 20:14:30 +01:00
findcasts.py addons: Change shebang to use Python 3 instead of Python 2 (#2361) 2019-11-15 21:38:20 +01:00
misc.py addons: Change shebang to use Python 3 instead of Python 2 (#2361) 2019-11-15 21:38:20 +01:00
misra.py addons: Change shebang to use Python 3 instead of Python 2 (#2361) 2019-11-15 21:38:20 +01:00
naming.json Feature/ros naming check (#1511) 2019-01-09 18:16:51 +01:00
naming.py addons: Change shebang to use Python 3 instead of Python 2 (#2361) 2019-11-15 21:38:20 +01:00
namingng.py addons/namingng.py: Fix some PEP 8 and Inspections warnings (#2351) 2019-11-12 09:47:48 +01:00
threadsafety.py addons: Change shebang to use Python 3 instead of Python 2 (#2361) 2019-11-15 21:38:20 +01:00
y2038.py addons: Change shebang to use Python 3 instead of Python 2 (#2361) 2019-11-15 21:38:20 +01:00

README.md

Cppcheck addons

Addons are scripts that analyses Cppcheck dump files to check compatibility with secure coding standards and to locate various issues.

Supported addons

  • cert.py Checks for compliance with the safe programming standard CERT.
  • misra.py Used to verify compliance with MISRA C 2012 - a proprietary set of guidelines to avoid such questionable code, developed for embedded systems. Since this standard is proprietary, cppcheck does not display error text by specifying only the number of violated rules (for example, [c2012-21.3]). If you want to display full texts for violated rules, you will need to create a text file containing MISRA rules, which you will have to pass when calling the script with --rule-texts key. Some examples of rule texts files available in tests directory.
  • y2038.py Checks Linux system for year 2038 problem safety. This required modified environment. See complete description here.
  • threadsafety.py Analyse Cppcheck dump files to locate threadsafety issues like static local objects used by multiple threads.

Usage

Command line interface

cppcheck --addon=cert --addon=y2038 src/test.c

It is also possible to call scripts as follows:

cppcheck --dump --quiet src/test.c
python cert.py src/test.c.dump
python misra.py --rules-texts=~/misra_rules.txt src/test.c.dump

This allows you to add additional parameters when calling the script (for example, --rule-tests for misra.py). The full list of available parameters can be found by calling any script with the --help flag.

GUI

When using the graphical interface cppcheck-gui, the selection and configuration of addons is carried out on the tab Addons and tools in the project settings (Edit Project File):

Screenshot