Idempotent loop
Continue reading
static code analysis
CMake
Buffer overflow
Continue reading
Apache Hive
Null Pointer Exception
Continue reading
.NET Core
A typo
Continue reading
Elasticsearch
Little method can go a long way
Continue reading
Microsoft Calculator
Incorrect string comparison
Continue reading
Free PVS-Studio for those who develops open source projects
In the New year 2019, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub or Bitbucket. They are given free usage of PVS-Studio static analyzer for development of open source projects.
Search for Bugs in Code at the Early Stage
Every developer knows about a debugger, version control system or, for example, unit-tests. Nevertheless, not all developers are familiar with the methodology of static code analysis. Meanwhile, the technology becomes an integral part of the development cycle of programs. I would like to suggest a small introductory course for anyone interested in modern development trends.
Myths about static analysis. The fifth myth – a small test program is enough to evaluate a tool
This is how this statement looks in discussions on forums (this is a collective image):
I’ve written a special program, its size is 100 code lines. But the analyzer doesn’t generate anything although all the warning levels are enabled. This [tool of yours] / [static analysis] in general is just rubbish.
Myths about static analysis. The fourth myth – programmers want to add their own rules into a static analyzer
No, they don’t. They actually want to solve some tasks of searching for particular language constructs. It is not the same thing as creating diagnostic rules.
