Running with multiple thread causes way less warnings to be found.

[anoy.]

I have noticed that much less warnings are generated when I run cppcheck with multiple threads.
When running cppcheck in one of my projects without -j, 109 warnings are found, with -j >= 2 only 40 warnings are found.

[Daniel Marjamäki]

What warning ids? Does it help when you use --cppcheck-build-dir?

[anoy.]

For this project some uninitMemberVar, internalAstError, useInitializationList and passedByValue are not found with threads.
Running with a extra --cppcheck-build-dir does noch change anything.

[Daniel Marjamäki]

I feel that it is unexpected if those warnings are not shown.

can you reproduce so the same warnings are missing every time or will it be different warnings?

so in the cppcheck build dir, cppcheck will write files. Do you see that these warnings are missing there too?

[Daniel Marjamäki]

is your project open source?

[anoy.]

The missing warnings are always the same.

In the build dir the warnings missing in the result, are found in both runs. Surprisingly when running with threads there are some noExplicitConstructor found additional (but were suppressed by my configuration)

No, the current project is not open source, but I could try to find one in our sources which behaves similar and ist (third-party) open (like KDSoap from my other issue).

[anoy.]

The attached zip contains part of the KDSoap code, a batch with the cppcheck calls and the generated results.

In this case the missing warnings are all noExplicitConstructor, but in other projects I've also got various other.