Mikael Heden

Hi, I have a suppression-list file and it is working fine. However, sometimes the suppression doesn't kick in for some reason. Here is an example: Snip from xml output file: <error id="misra-c2012-5.6" severity="style" msg="A typedef name shall be a unique identifier" verbose="A typedef name shall be a unique identifier"> <location file="lib\src\Misc\Typedef.c" line="44" column="5"/> </error> <error id="misra-c2012-5.6" severity="style" msg="A typedef name shall be a unique identifier" verbose="A...

Hi, I have a suppression-list file and it is working fine. However, sometimes the suppression doesn't kick in for some reason. Here is an example: Snip from xml output file: <error id="misra-c2012-5.6" severity="style" msg="A typedef name shall be a unique identifier" verbose="A typedef name shall be a unique identifier"> <location file="lib\src\Misc\Typedef.c" line="44" column="5"/> </error> <error id="misra-c2012-5.6" severity="style" msg="A typedef name shall be a unique identifier" verbose="A...

When browsing the issue tracker some more, I found this ticket: #12817 (Reporting: Output Cert level and Misra classification) – Cppcheck So I guess it is not possible at the moment.

Hi, Is there a way of extracting the Misra Category (mandatory, required, advisory), in a template? As far as I can tell, it is added as an extra value to the report (in the cppcheckdata.reportError call in reportError in misra.py). But I can't seem to get it from cppcheck, neither via templates nor xml output.

With --addon together with --cppcheck-build-dir it seem to be putting the dump files in the build folder. The only drawback I can see is that the folder structure is not preserved in the build-dir (i.e. all files ends up in the root).

I guess it apply to both, as far as I can tell, both --dump and --addon (at least --addon misra) are creating .dump files adjacent to the source file.

This would be a great feature, I like to build in a separate out directory and right now the dump files "pollutes" the source tree. Either a --dumpdir or a --dumpprefix flag would be very useful. Or maybe use the already existing --cppcheck-build-dir for this? Thanks!