Georgiy Komarov

Is the cert.py addon only available in the commercial version? Yes. It was removed here: https://github.com/danmar/cppcheck/commit/92316b07c8a016496f19ea91181927b60d713c2c . You can probably make it work by just restoring the Python script.

Hello Peter, You can copy the rule texts from “Appendix A - Summary of guidelines” from the PDF and paste those into the text file. Everything should work. Here is an example of correct rules text used in tests: https://github.com/danmar/cppcheck/blob/ec13f5fe5c27488f4b03caf153637ce1846d0c0b/addons/test/misra/misra2012_rules_dummy_ascii.txt#L1 .

I can't confirm crash for this case, but there is an internal error. Here is output on the both examples for cppcheck from main branch (commit 27d7609d): ~/D/cppcheck  main ./cppcheck --enable=unusedFunction test.cpp Checking test.cpp ... test.cpp:0:0: error: Internal error. Token::linkAt called with index outside the tokens range. [cppcheckError] ^ test.cpp:6:0: style: The function 'clamp' is never used. [unusedFunction] ^ ~/D/cppcheck  main ./cppcheck --enable=all --std=c++11 --library=qt test.cpp...

Well, this error message was recently added: https://github.com/danmar/cppcheck/pull/3343/files . But the format of the rules files has not been changed. Only error message was added. So, this error with suppressions was even when you were using Cppcheck 2.1, but you didn't see any errors. I'm not sure about the format of rule files from your message. You need something like this: Appendix A Summary of guidelines Rule 1.1 Required text of rule 1.1 Rule 1.2 Advisory text of rule 1.2 etc.

It's okay to report some bugs here. But for convenience, you can ask for Trac account from Daniel, as described here.

Thanks! The problem is in Cppcheck itself. I created the following ticket: https://trac.cppcheck.net/ticket/10376 .

I'm not sure about the question in the OP post. But here is my understanding of the example in the test suite. The first example has a rvalue with 5U value, without explicit specification of the type. The MISRA document introduces a definition of Unsigned Type of Lowest Rank (UTLR) in Appendix D3. This roughly means the minimal possible unsigned type that can hold the given value. uint8_t can store 5U value, so there is no error. The second example provides the explicit cast of the result to the...

Well, according to git blame, this was my fix for the false negative in rule 10.1: https://trac.cppcheck.net/ticket/9489 . This ticket contains a link to the following line in the example suite: https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/blob/master/R_10_01.c#L77 . So, the test clearly implements this case.