Mark Donkers

Hi Daniel. Thanks for the invitation to participate. I will seriously consider it!

Hi David, Thanks for the quick reply. It's a shame this hasn't been fixed yet - I was hopeful that this would be a great a static analysis tool for our team. We will have to accept the workaround for now. Cheers, Mark On Wed, 27 Mar 2019 at 20:26, David excsniper@users.sourceforge.net wrote: Hi Mark, Unfortunately I had just accepted the random results problem for what it is and basically did what you outlined in your "Output changes on each analysis" post. As for clang-tidy, it took a bit of time...

Hi David, Did you get any further with the two issues that you presented in this thread? I'm also new to Cppcheck and clang-tidy and am having the exact issues that you're having. The code that I'm trying to 'lint' comes from an Eclipse based IDE and so there is no make file (as far as I know), so importing is not an option. Thanks for any insight that you can share, no matter how little. Mark

Each time I perform an analysis on my project (on an unchanged code base), the number of outputted errors/warnings/information randomly changes. I would think that the output should always be identical since nothing has changed. Further down are the statisics from two back-to-back scans. Version: Cppcheck v1.87 Note: Performing a "Clear results" between scans does not fix it. Workaround 1: Close Cppcheck, reopen and press "Reanalyze all files" Workaround 2: Delete the myproject-cppcheck-build-dir...