Tofik Sonono

Thanks for your that, that did indeed remove all the errors from the ignored paths, and no more suppressed errors appear as well. Everything seems to work now. I did however notice that suppression do still appear when running cppcheck in multithreaded mode, e.g when I run the command I posted in my initial post in multithreaded (without pwd and adding -j12 or -j2) will still generate suppressed errors (not in ignored paths). Just wanted to bring that to light.

Yes sorry, I was short on time. I did some more investigating and it seems like the suppressed errors that I'm getting are actually from the directories I've ignored. As you can see on the command I ran from my initial post, it includes -i$(pwd)/external. However, I'm still getting errors from my external directories. I figured this was due to using ignore (-i) option combined with --project which then in turn will make cppcheck not respect the paths you want to ignore. But now I'm noticing that...

Yes sorry, I was short on time. I did some more investigating and it seems like the suppressed errors that I'm getting are actually from the directories I've ignored. As you can see on the command I ran from my initial post, it includes -i$(pwd)/external. However, I'm still getting errors from my external directories. I figured this was due to using ignore (-i) option combined with --project which then in turn will make cppcheck not respect the paths you want to ignore. But now I'm noticing that...

Yes sorry, I was short on time. I did some more investigating and it seems like the suppressed errors that I'm getting are actually from the directory I've ignored. As you can see on the command I ran from my initial post, it includes -i$(pwd)/external. However, I'm still getting errors from my external directories. I figured this was due to using ignore (-i) option combined with --project which then in turn will make cppcheck not respect the paths you want to ignore. But now I'm noticing that all...

Hi again, thanks for the reply. I'm using cppcheck 2.5 from Fedora dnf repos. In my case, it's actually both the misra and core warnings which I have suppressed that still show up in the plist files.

Hi, I'm running cppcheck with a compile_commands file, a couple of suppressions and plist output (for usage with ericsson codechecker). The problem I'm experiencing is that plist entries are generated for the findings that are suppressed, even though that the suppressed findings are not displayed in the cli output. Am I missing something, or is this expected behavior / bug? cppcheck -i$(pwd)/external --project=build/compile_commands.json --enable=all plist-output=./reports --suppress=objectIndex...

Hi, I'm running cppcheck with a compile_commands file, a couple of suppressions and plist output (for usage with ericsson codechecker). The problem I'm experiencing is that plist entries are generated for the findings that are suppressed, even though that the suppressed findings are not displayed in the cli output. Am I missing something, or is this expected behavior / bug? cppcheck --quiet -i$(pwd)/external --project=build/compile_commands.json --enable=all plist-output=./reports --suppress=objectIndex...