The 'sizeof (bs->teamleader)' index is pointing beyond array bound. The error was found through the V557 diagnostic: Array overrun is possible. Array overrun (incorrect expression).Ĭhar teamleader //netname of the team leaderīs->teamleader = '\0' The correct code is: "findWhat = '\0' ".Įxample 7.Wolfenstein 3D project. The terminal null is written outside the array. This error is a kind of the previous one. The '64' index is pointing beyond array bound. Void CG_RegisterItemVisuals( int itemNum ) But we think any C/C++ programmer understands how numerous and insidious they are.Įxample 1.Wolfenstein 3D project. In the article we will show just a small part of these errors found by the PVS-Studio analyzer. This is the price for the capability of effective low-level memory handling available to programmers. This is the list of analyzed projects:Įrrors of array and string handling are the largest class of defects in C/C++ programs. If we described all the found defects, it would be a reference book.
Of course, we have taken just a few errors from each of the projects. One and the same error can often be referred to misprints and incorrect array handling at a time. The samples of detected errors will be divided into several groups. Samples of errors detected in various open-source projects Please see our post " FAQ for those who have read our articles". Those who want to know what PVS-Studio is and download the trial version, see this page. Those who want to know what static code analysis is, please follow the link. We won't tire you programmers by making you read texts and will pass to the error samples right away. All the errors have been found with the PVS-Studio static code analyzer. The readers are offered to study the samples of one hundred errors found in open-source projects in C/C++. This article demonstrates capabilities of the static code analysis methodology.
0 kommentar(er)
