• The first step towards PVS-Studio for C#

    The PVS-Studio team would like to share some news and heat up the audience interest a bit. We have started C# analyzer development. From the user's point of view it'll still be our good old PVS-Studio, but now we'll teach it how to look for bugs in C# programs. Read more
  • Checking Appleseed source code

    Majority of the projects we report about in the articles contain dozens of PVS-Studio analyzer warnings. Of course we choose just a small portion of data from the analyzer report to be in our articles. There are some projects though, where the quantity of warnings is not that high and the number of some interesting "bloomers" is just not enough for an article. Usually these are small projects, which ceased developing. Today I'm going to tell you about Appleseed project check, the code of which we found quite high-quality, from the point of view of the analyzer. Read more
  • Unicorns...they are everywhere...

    I'm excited to share some news with our fans of PVS-Studio and unicorns. Now you can see our logo not only on our web-site and the check reports of open - source projects, but also on T-shirts, mugs and even wallpapers. How to get all of that? Here is the story. Read more
  • Static Analysis of Mozilla Thunderbird's Code by PVS-Studio

    In this article, we will talk about the analysis of the Mozilla Thunderbird project by the PVS-Studio static analyzer. Being a Thunderbird user, I would occasionally run into hangs and strange behavior of the program. Hopefully our analysis will help to reveal at least some of the reasons behind it in the source code. So welcome to follow me to see what errors can be found in this popular project. Read more
  • Analysis of Telegram by PVS-Studio and Vice Versa

    It's interesting to analyze projects and doubly so to analyze well-known projects, especially when you use them yourself. Even more interesting it would be to analyze a project with high-quality code - it would let you kill two birds with one stone: scan the project itself, proving or disproving the declared quality, and also see how well the analyzer has done its job. Having pondering this a bit, I decided the popular messenger Telegram would suit us best for this task. Read more
  • Documenting Bugs in Doxygen

    In this article, we will speak about the static analysis of the doxygen documentation generator tool. This popular and widely used project, which, as its authors claim, not without reason, has become "the de facto standard tool for generating documentation from annotated C++ sources", has never been scanned by PVS-Studio before. Doxygen scans the program source code and generates the documentation relying on it. Now it's time for us to peep into its source files and see if PVS-Studio can find any interesting bugs there. Read more
  • PVS-Studio Meets Octave

    In this article, I'm going to tell you about my experience of analyzing the Octave project. It is quite a popular one, especially among students who need to scan their math task solutions yet don't feel like buying a Matlab license. Read more
  • 80% of PVS-Studio Downloads Done by Aliens or Is the Problem on Our Side?

    In our PVS-Studio team, we are very fond of measuring things. Besides money we earn and salaries and taxes we pay, we also like to measure the number of PVS-Studio downloads, installations, percent distribution across IDEs, and so on. Sometimes these measurements suggest very important conclusions. But at other times they just embarrass us. In this article, I'd like to tell you about one case of this kind and ask for help. Read more
  • How to Port a 9 Million Code Line Project to 64 bits?

    Our team has recently finished porting one pretty large project (9 million code lines, 300 Mbytes of source files) to the 64-bit platform. It took us one year and a half. Although we are not permitted by the NDA to disclose the project name, we still hope that our experience will help other developers in their work. Read more
  • Viewing Bug Statistics, or "Look, They've Got Charts in PVS-Studio!"

    This post will be first of all of utmost interest to project and technical managers whose teams use the PVS-Studio code analyzer in their projects. We have recently implemented a new feature to let you monitor the efficiency of the team tool use. You can finally have the necessary figures to prove to your boss that the analyzer which cost your team or company a few thousands of dollars is bringing a real, tangible profit. But don't worry – this article is not about ROI at all. Read more