Thanassis Tsiodras

I'll just patch it directly on my side, doing string replacing in the hashData (since I know the baseline paths - "/builds/RANDOMPREFIX_TO_REMOVE"). But it would be nice if cppcheck didn't use the complete paths when creating the suppressions - and instead used the "path from baseline top folder". This would work for any one who tries to do the same in the future.

I added std::cout << "Hashing this:" << hashData << std::endl; ...and a corresponding include of iostream. And sadly, in the first few lines of the output, I saw it: <suppression errorId="nullPointerRedundantCheck" fileName="FULLPATHTOSRC"... We are indeed using suppressions, but our suppressions.xml doesn't contain full paths. It seems cppcheck creates full paths after parsing it, and then uses the full paths to do the hashing. Damn.

You mean the toolinfo.str(), right? (at cppcheck.cpp:717)

You mean the toolinfo.str(), right? (at line 717)

You mean the toolinfo.str(), right?

So you observe that the .a1 files are recreated every time? Correct - they do. In the meantime, I also tried copying across the .snalyzerinfo files that are also generated. I even made sure their timestamps are later than those of the .c files - i.e. my CI script after the copy it touches them: find src -type f -iname '*zerinfo' -exec touch '{}' ';' Still nothing - everything is regenerated every time. To be clear: if I do the rebuild myself from inside the same folder that the CI did it, the second...

So you observe that the .a1 files are recreated every time? Correct - they do. In the meantime, I also tried copying across the .snalyzerinfo files that are also generated. I even made sure their timestamps are later than than .c files: $ find src -type f -iname '*zerinfo' -exec touch '{}' ';' Still nothing - everything is regenerated every time. To be clear: if I do the rebuild myself from inside the same folder that the CI did it, the second time everything goes fast (no reprocessing). The issue...

I have configured cppcheck to continually process a source codebase with our continuous integration machinery. It takes a lot of time to process our codebase, though - and since most of the source files (C/C++) don't change per commit, I wanted to reuse the previous scans as much as possible. What I tried in our CI build script: cd src mkdir cppcheck-cache cp -a $HOME/cppcheck-cache/* cppcheck-cache/ bear -- make all # builds the compile_commands.json cppcheck ... --project=$PWD/compile_commands.json...