Blog

  • PVS-Studio and Hostile Environment

    28.01.2015
    This is another story about programs having a hard time trying to interact with the external world. At first glance, a static analyzer should face no problems at all. It just gets files and some additional information at the input and generates a log-file out of it. But the Devil is, as usual, in the detail. Read more
  • Twitter for C++ Programmers (updated)

    23.01.2015
    This small post is for those programmers who use Twitter or are just about to start doing this. I'm sure developers will find some useful information here. Read more
  • Reflections on the Null Pointer Dereferencing Issue

    15.01.2015
    As I have recently found out, the question whether or not the code &((T*)(0)->x) is correct appears to be quite complicated. I decided to write a small post on this subject. Read more
  • PVS-Studio Probes into Linux' Innards (3.18.1)

    03.01.2015
    For the sake of advertisement, we decided to analyze the Linux kernel with our static code analyzer. The difficulty of this task makes it especially interesting. Linux' source codes have been checked and are still checked by numbers of different tools. So finding anything new was hardly probable. But if we succeeded, it would be a nice advertisement for the PVS-Studio analyzer's capabilities. Read more
  • Note about diagnostics fine-tuning

    15.12.2014
    Despite the fact that our analyzer is stated to be one of the simplest tools in installing and everyday usage (everything is working "out-of-the-box" and does not require any unintuitive tweaks), some users lacks flexibility of some of the diagnostic rules. Unfortunately, usability and flexibility is if not totally opposite, but sometimes those features conflict with each other. In this note, we shall be talking about additional mechanism of tuning some diagnostic rules, which can be useful for some of our valuable users. Read more
  • Why Students Need the CppCat Code Analyzer

    10.12.2014
    CppCat is a simple static code analyzer capable of detecting bugs in C/C++ programs. We started granting free academic licenses to all interested (students, teachers, and so on). For the sake of popularizing CppCat among students, I decided to write this post about errors that can be found in student lab work tasks posted at Pastebin.com. Read more
  • Miranda NG Project to Get the "Wild Pointers" Award (Part 2)

    28.11.2014
    In this article, we continue to discuss errors found in the Miranda NG project by the PVS-Studio static code analyzer. Last time we were talking about pointers and memory handling. This time we are going to talk about general errors most of which are due to programmers' inattentiveness and typos. Read more
  • Miranda NG Project to Get the "Wild Pointers" Award (Part 1)

    25.11.2014
    I have recently got to the Miranda NG project and checked it with the PVS-Studio code analyzer. And I'm afraid this is the worst project in regard to memory and pointers handling issues I've ever seen. Although I didn't study the analysis results too thoroughly, there still were so many errors that I had to split the material into 2 articles. The first of them is devoted to pointers and the second to all the rest stuff. Enjoy reading and don't forget your popcorn. Read more
  • Free CppCat for Students

    13.11.2014
    CppCat is a static code analyzer integrating into the Visual Studio 2010-2013 environment. The analyzer is designed for regular use and allows detecting a large number of various errors and typos in programs written in C and C++. For the purpose of popularizing it, we've decided to launch a student-support program granting free licenses to every higher school student who will contact and ask us about that. You just need to send us a photo of your student card or transcript. Read more
  • A Slipshod Check of the Visual C++ 2013 Library (update 3)

    13.10.2014
    Someone suggested to me recently that I check the libraries from Visual Studio 2013. I haven't found anything of much interest, just a few small errors and slip-ups. They wouldn't make an interesting, attractive article, but I've still decided to describe all those defects. I just hope it will help make the libraries a bit better and stimulate the authors to carry out a more thorough analysis. I don't have the project files necessary to build the libraries, so my analysis had to be superficial and I could have missed a lot. Read more