Bug 44670 - Errors in the source code found by PVS-Studio static code analyzer.
Summary: Errors in the source code found by PVS-Studio static code analyzer.
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: General ()
Version: unspecified
Hardware: PC All
: --- enhancement
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-09-23 08:00 UTC by Sergey Vasiliev
Modified: 2018-03-13 15:03 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 44670 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Sergey Vasiliev 2016-09-23 08:00:04 UTC
During the analysis of ‘Mono’ with the help of PVS-Studio static code analyzer we, managed to find several fragments that have errors or just look suspicious. Some of them are described in the article on the official site of PVS-Studio: http://www.viva64.com/en/b/0431/
Nevertheless, several suspicious fragments weren’t covered in this article, that’s why I would suggest checking the code of the project yourself with PVS-Studio.