Skip to content
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

Resolve issues found by PVS (static analysis tool) #415

Closed
demoth opened this issue Jul 19, 2019 · 3 comments

Comments

@demoth
Copy link

commented Jul 19, 2019

@TimeDoctor

This comment has been minimized.

Copy link
Member

commented Jul 19, 2019

Please feel free to discuss strategies for fixing issues found with scanning utilities on our forums at discourse.ioquake.org . This report as it is, especially including third-party code we don’t control, is not tremendously helpful as an issue although I appreciate the time you took to run it.

@TimeDoctor TimeDoctor closed this Jul 19, 2019

@demoth

This comment has been minimized.

Copy link
Author

commented Jul 19, 2019

@TimeDoctor The idea behind this exercise was to highlight suspicious places in the code so other may take a look and improve.
I agree thirdparty code is not very interesting - I filtered it out.

@ensiform

This comment has been minimized.

Copy link

commented Jul 19, 2019

A lot of these are actually false positives anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.