cppcheck

[jacobnavia]

Hi
Has anyone here used this static analyzer?

For C projects it seems to work, but for C++ code it hangs (I stopped
after waiting for 6 hours for any output).

I am using it in an ARM64, about 5 times slower than a high end PC.

Is this normal?

Thanks for any info

jacob

[Ian Collins]

On 01/02/2018 01:57 PM, jacobnavia wrote:
> Hi
> Has anyone here used this static analyzer?

Yes, my current project uses it (version 1.79 works best for me) on all
of our C and C++ code.

> For C projects it seems to work, but for C++ code it hangs (I stopped
> after waiting for 6 hours for any output).

Which version and options? It will work significantly faster on Linux
than it does on Windows.

> I am using it in an ARM64, about 5 times slower than a high end PC.
>
> Is this normal?

Probably, why not just use it on the PC? Using -j 2*core count should
speed things along nicely.

--
Ian.

[Rick C. Hodgin]

I have used Visual Studio's built in Code Analyzer. It found half
a dozen rare / extreme-case bugs. I haven't tried Visual Studio 2017's
Code Analyzer yet. Just VS 2015. It's integrated into the GUI, and
enabled by a simple compile option. Compilation takes 2x to 5x longer
than normal. Explains step-by-step conditions which yield the code in
error scenario.

--
Rick C. Hodgin

[Andrea Venturoli]

On 01/02/18 01:57, jacobnavia wrote:
> Hi
> Has anyone here used this static analyzer?

Yes.

> For C projects it seems to work, but for C++ code it hangs (I stopped
> after waiting for 6 hours for any output).

I'm using it on C++, and it's doing partly its job: I get a lot of false
positives (always of the same 2 or 3 types however), but it did find
some faults in the code.

> I am using it in an ARM64, about 5 times slower than a high end PC.
>
> Is this normal?

No.
While it's slow, I never had to wait 6 hours.



bye
av.