Since , the updates for this blog stopped, but the developers hope that "bug of the month" can be started again in the future. In the meantime, we decided to take the baton from PC-Lint and create our own "bug of the month" with blackja.. As it was already said, we reviewed our existing error base and the always up-to-date list of open source projects. Perhaps, these materials would be interesting and also useful to the readers, as they can be used as recommendations of how to avoid the same errors, they may also help in doing some researches, related to the improvement of the software reliability and even for working on the code standards.
The existence of a large amount of errors in the code especially in big projects can be explained by the fact that it's not always possible to hold the attention and control every line of code, especially when there are thousands of them.
This is how Copy-paste errors, undefined behavior, null pointer dereference, typos and other errors get in the code. They could all be avoided with the help of static analysis. To make the number of such bugs less and improve the quality of the code, we suggest downloading and trying PVS-Studio on your project. Who knows, may be you will find your own bug of the month and will tell about it the community of developers to protect them from such errors. For now, you could also practise your bug searching skills and look for bugs in well-known Open Source projects.
Recently, in the newly released version of PVS-Studio 6. So, welcome: Bug of the month! This is your promo code:. To get a trial key fill out the form below. Why do we ask to use business email?
Team License a basic version. Enterprise License an extended version. Didn't get our email? New License. License Renewal. I am a reseller. Ask us your question. Why do we ask to use Business Email? To get the licence for your open-source project, please fill out this form. I am interested to try it on the platforms:. PVS-Studio for. NET Core. JetBrains Rider.
Bug of the month: taking the baton from…. Ekaterina Matveeva. Mar 23 Author: Ekaterina Matveeva. Subscribe to our newsletter. Tags: Marketing. Popular related articles. Date: Jul 31 Author: Andrey Karpov. After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors how many erro….
The Evil within the Comparison Functions. Date: May 19 Author: Andrey Karpov. Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…. Date: Jan 30 Author: Andrey Karpov. Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho….
Date: Oct 22 Author: Andrey Karpov. Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…. PVS-Studio for Java. Date: Jan 17 Author: Andrey Karpov. It's time for a brief story of how we've started making support of the Java language, how far we've co…. Detect bugs that can waste countless hours of developer and end user time before they're found.
Developers spend a significant portion of their time attempting to identify the source of reported bugs based on surface-level errors that impact the use of the software. PC-lint Plus goes straight to the root cause and identifies specific actionable issues associated with a particular piece of code so that they can be fixed before they cause runtime errors.
Levarage the parallel computation capabilities of modern hardware to quickly analyze large projects. PC-lint Plus scales efficiently to utilize multiple processing cores by using independent threads and minimal shared memory. Developers and testers can perform code analysis on individual workstations or query results from a build server automatically analyzing every code change.
Our message suppression system makes it easy to get started by focusing on the most relevant diagnostics. It is flexible enough to support the needs of large projects involving multiple teams, guidelines, and exemptions.
Modular configuration files can be organized to provide a standard analysis environment. PC-lint Plus runs locally on your developer workstations, build servers, or continuous integration servers. It does not use an internet connection and will never collect nor submit data, code, statistics, analytics, or any other information from your system over any channel. Download a free day evaluation license to try PC-lint Plus locally and see the value it can bring to your project.
During the evaluation you will have full access to our technical support team. Visit our online technical demonstration for a sample of PC-lint Plus analysis on an editable code example. See how PC-lint Plus can help you:. Comply with Safety Standards. Detect critical bugs and vulnerabilities such as buffer overflows, null pointer dereferences, inappropriate interface use, and undefined behavior by providing constructive diagnostics. Identify code that is brittle, difficult to maintain, invokes implementation-defined behavior, or is otherwise suspicious, in order to reduce the potential for defects to develop in the first place.
Avoid wasted time spent tracking down bugs and identify issues proactively during the development process. Widely Compatible. Runs natively on Windows, Linux, and macOS. Analyze source code targeting virtually any platform. Fully multi-threaded operation allows analysis of large projects to efficiently scale across multiple cores to take full advantage of the available hardware.
0コメント