Grahame White

You're welcome, glad you found it helpful.

I don't have an account for the bugtracker, so I'll attach my sample code, along with screenshot of it failing here. This sample fails 100% of the time for me. Looking over my production code that has these failures it only appears that the first if statement inside the else clause triggers a false positive.

Using the MISRA-C:2012 plugin I'm seeing a number of, what look to me to be false positive, warnings. The rule states that all if ... else if constructs should be terminated with an else, using the following example I don't believe that there should be a warning, however one does get raised. void SomeFunction(void) { if (true) { SomeFunction(); } else { if (false) { SomeFunction(); } // Should this really fail here? } } I'm using cppcheck 1.87 via the GUI. On the subject of this particular MISRA-C...

Thanks for your reply, that was very helpful. Unfortunately, I did not find Chapter 8 of the manual to be as helpful as it could be. It does explain nicely how to process the MISRA C pdf to generate a usable text file. It doesn't explain clearly how to run the misra plugin (or any other plug in for that matter) * I didn't find it all that clear that the main cppcheck code was unable to trigger the addons. Once I've got things working from my end I'll take a look at writing something for inclusion...

I built the tagged 1.87 release of cppcheck on a linux machine using the make -j 8 SRCDIR=build CFGDIR=/usr/share/cppcheck/cfg HAVE_RULES=yes CXXFLAGS="-O2 -DNDEBUG -Wall -Wno-sign-compare -Wno-unused-function -lpcre" install Aside from a few warnings, the build was succesful and I'm able to run cppcheck against a test C project However, when I wanted to add in the MISRA-C 2012 checks things don't go quite as smoothly. I'm calling cppcheck using the following commandline options from the root of...

I've been adding unit tests to some legacy code with a reasonable level of success....