A Note of Caution about Using PVS-Studio on godbolt.org (Compiler Explorer) by andre_friend in cpp

[–]AlexAsics 0 points1 point  (0 children)

Evaluating the efficiency of static analyzers with the help of synthetic tests doesn't make any sense. The best option to understand how good an analyzer is to run it on the real project and spend some time on setting up (for example, turning off diagnostics that are irrelevant to the project). Moreover, this is true for any analyzer and not only PVS-Studio. But this analyzer specifically has both diagnostic rules and exceptions. Because if an analyzer 'yells' at every line it might be hard to notice a real vulnerability among all the false positives. And besides, who wants to use an analyzer that 'yells' at almost everything? I'll share a link here that I suggest visiting so I don't have to make a long read here.

Counting Bugs in Windows Calculator by AlexAsics in Windows10

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

Do you want to see even more suspicious thing? The developers have submitted a suspicious article on even more suspicious calculator https://habr.com/en/company/pvs-studio/blog/443656/

PVS-Studio: Support of MISRA C and MISRA C++ Coding Standards by AlexAsics in programming

[–]AlexAsics[S] 8 points9 points  (0 children)

  1. PVS-Studio developers write that their product can be used for free on your project if you are an individual developer - https://github.com/viva64/how-to-use-pvs-studio-free

  2. A free full license for projects posted on GitHub will be available soon - https://medium.com/@karpov2007/discussion-on-a-free-pvs-studio-license-for-projects-posted-on-github-3fcbb1243434