-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Year PVS-Studio 6.00 Release: Scanning Roslyn #7677
Comments
The log file is available here: https://www.dropbox.com/s/6l6zw71eqkbps0x/Roslyn.zip?dl=0 |
Got the log, thanks. 246 errors. Will take a look after the holidays V3002: The switch statement does not cover all values of the 'CommandIds' enum: BreakLine, ExecuteInInteractiveWindow, CopyToInteractiveWindow. [src\InteractiveWindow\VisualStudio\VsInteractiveWindowCommandFilter.cs : 418]
|
Guys, some additional info. The best way to review our plog file is to install PVS-Studio, open the plog file and start jumping into the code to review the code fragments that the warnings were issued for. If you change the code (the plog file is created by December 18), we advise to recheck the project. In the PVS-Studio trial mode, there are only 50 jump-clicks to the code from the list of warnings. Please contact us - [email protected] when you decide to fix the issues. We can give you a license key for two weeks. So, you can use the full capacity of the tool without any limitations. |
@pvs-studio Or you could use any text editor to jump to the noted source line. |
Corrects a couple of items noted in dotnet#7677
@jaredpar Can you cross out the ones you looked at and fixed or dismissed as noise? |
@davkean that's the plan once this is merged in. I've been keeping track of everything I updated. |
@AndreyKarpov thanks for the analysis, but it appears there's a lot of false positions in this analysis, some examples, picking some random ones that I looked at:
|
@davkean Yes, false positives do happen, although it shouldn't be surprising. It would be strange to expect that such a qualitative project as Roslyn will have a big number of real bugs. Also, I always emphasize that the real value of the analyzer is in its regular use, not in occasional checks. In any case we are still working on the quality improvement of our tool. I hope that further versions will generate less false positives. The issues with false positives can be tackled in many different ways. For example if you want to start using the analyzer regularly, the most comfortable method will be "mark up base". More details: http://www.viva64.com/en/b/0364/ |
Moving these to the areas impacted by the list of files to see if there's any work to still do. Infrastructure isn't a vacuum cleaning service for other team's code. 😄 |
Unlikely to do anything here. |
The long wait is finally over. We have released a static code analyzer PVS-Studio 6.00 that supports analysis of C# projects. Now it can analyze projects written in languages C, C++, C++/CLI, C++/CX, and C#. For this release, we have prepared a report about analysis of open-source project Roslyn. It is thanks to Roslyn that we were able to add the C# support to PVS-Studio, and we are very grateful to Microsoft for this project.
Article: http://www.viva64.com/en/b/0363/
The text was updated successfully, but these errors were encountered: