はてなブックマーク

No. 10. What operating system are we running on?No. 9. Who's first?No. 8. Dangerous bitwise operationsNo. 7. Variables mixed upNo. 6. C++ has its own lawsNo. 5. What's at the end of the line?No. 4. The magic constant PiA small diversionNo. 3. An elusive exceptionNo. 2. Unclosed HTML tagsNo. 1. Elusive standard functionsConclusion Another year is drawing to an end, and it's a perfect time to make y

Linux Kernel, tested by the Linux-version of PVS-Studio How we did the checkTyposUnused variablesConfusion in the operation precedenceSuspicious checksAn erron in a macroMeaningless memsetDangerous use of memcmpConclusion Since the release of the publicly available Linux-version of PVS-Studio, it was just a matter of time until we would recheck the Linux kernel. It is quite a challenge for any sta

The Ultimate Question of Programming, Refactoring, and Everything Preface1. Don't do the compiler's job2. Larger than 0 does not mean 13. Copy once, check twice4. Beware of the ?: operator and enclose it in parentheses5. Use available tools to analyze your code6. Check all the fragments where a pointer is explicitly cast to integer types7. Do not call the alloca() function inside loops8. Remember

Unreal EngineAnalysis methodology for an nmake-based projectAnalysis resultsTyposNull pointersA few more words about null pointersExcess variable declarationErrors in function callsA variable assigned to itselfThe nicest of all the errorsA break operator missingMicrooptimizationsSuspicious sumMess-up with enumA logical errorSuspicious shiftObsolete checksCopy-PasteMiscellaneousConclusions On March

A few words about Vim for a startNow about the check itselfAn excessive checkA strange memsetA strange loopScopesAn error with signed and unsigned types in one expressionA pointer initialized to NULL and not changed anywhere while still being usedUnsafe use of reallocA few false positivesPoorly written code where only the first byte of a structure is filledThe poor practice of using short namesA s

We develop a static analyzer for C, C++, C#, and Java code

Errors detected in Open Source projects by the PVS-Studio developers through static analysis We regularly check various open-source projects with PVS-Studio and send analysis results to developers and usually describe them in our posts as well. Besides, we add them into our bug database. This database is posted below on this page. The bugs are grouped according to the number of the diagnostic rule

Introduction1. Disabled warnings2. Use of functions with a variable number of arguments3. Magic numbers4. Storing integers in double type5. Bit shifting operations6. Storing of pointer addresses7. Memsize types in unions8. Changing an array type9. Virtual functions with arguments of memsize type10. Serialization and data exchangeThe use of types of volatile sizeIgnoring of the byte order11. Bit fi

This course was developed in 2010. However, it hasn't become obsolete and the information given in it is relevant enough for modern Visual Studio versions. The course is devoted to the creation of 64-bit applications in C/C++ language, and is intended for Windows developers who use the Visual Studio 2005/2008/2010 environment. Developers working with other 64-bit operating systems will learn many