Companies can also buy our product and get quick and detailed support along with the license. To do this, PVS-Studio provides free trial and free modes of using. Developers or enthusiasts can easily conduct an in-depth analysis by testing Unity themselves. I have not studied absolutely all the warnings, because there were quite a lot of them. As a result, I got 181 warnings of the first level of certainty (High) and 506 warnings of the second level of certainty (Medium). Getting rid of the warnings with low certainty, I made the analysis of the Unity source code. These settings are available in the drop-down menu of PVS-Studio in Visual Studio development environment, and in the parameters of the analyzer. I’ve also activated the warnings suppression mechanism of the third level of certainty (Low). Before the analysis, I’ve slightly simplified the work, having enabled the mode of the code display according to the CWE classification for the found bugs. It’s a lot, and the analyzer had a quite considerable scope. Especially since the amount of the source Unity C#-code, presented on GitHub, is about 400 thousand lines (excluding empty) in 2058 files with the extension “cs”. How did Unity please us this time? I’m saying “please” and hope not to offend the authors of the project. However, the author of the article managed to find quite interesting bugs. At that time so much C#-code was not available for the analysis: some components, libraries and examples of usage. Previously we’ve written an article about checking Unity.
0 kommentar(er)
