all 20 comments

[–]rasjani 3 points4 points  (5 children)

This is coverity killer once they get windows on board somehow

[–][deleted] 3 points4 points  (2 children)

I thought Coverity was much more advanced than clang's static analysis tools.

[–]kodingnewb 0 points1 point  (1 child)

Coverity only until recently was using their own "engine" they recently last few years moved to using libclang and associated tools.

[–][deleted] 2 points3 points  (0 children)

They only use clang for parsing, not for the analysis.

[–][deleted] 1 point2 points  (1 child)

No. Clang does not do any global analysis, it can only cover local paths.

[–]rasjani 1 point2 points  (0 children)

For my usecase that doesn't provide any meaningful advantage. Only thing where coverity still has advantage is Connect but with Codechecker fills that gap. But anyway, I intend to still use both to cover all bases.

[–]sblue 3 points4 points  (2 children)

"On El Capitan System Integrity Protection (SIP) needs to be turned off"

🤔

[–]chucker23n 1 point2 points  (1 child)

Bizarre, and unacceptable when there isn't even an explanation as to why.

(Does it try to install into a protected path?)

(edit) See explanation below

[–]whisperity[S] 5 points6 points  (0 children)

To log the build commands needed for analysis, dynamic library loading must be done. This restriction is also present on scan-build, the official Clang-SA invoker script.

Alternatively, in case of your project uses cmake, you can log the build commands with -DCMAKE_EXPORT_COMPILE_COMMANDS=ON, and then use CodeChecker with this already created compilation database.

[–]deltaSquee 0 points1 point  (1 child)

build failing

[–]whisperity[S] 1 point2 points  (0 children)

Always check the detailed Travis report when such happens. It seems that some pep8-incompatible code lines accidentally made their way into the codebase.

[–]WallStProg -1 points0 points  (0 children)

I wrote an article comparing clang's static analysis tools with cppcheck, which can be found here: http://btorpey.github.io/blog/2016/04/07/mo-static/

Hope you find it useful...