-
-
Notifications
You must be signed in to change notification settings - Fork 43
QEP 337: Coverity Scan cleanup #337
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
Conversation
Thank you for submitting your proposal to the 2025 QGIS Grant Programme. The 2 week discussion period ends today. At the end of the discussion, the proposal author has to provide a 3-line pitch of their proposal for the voter information material. (For an example from last year check qgis/PSC#58 (comment)) |
@anitagraser here you go: This project describes a widespread cleanup to QGIS' Coverity Scan static code analysis results, in order to make it easier for developers to identify high-impact issues reported by the Coverity Scan tool. There were no issues raised in the discussion. |
+1 |
6 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
The Coverity Scan tool is a highly regarded tool for static analysis of complex c++ projects. It's able to pro-actively identify many code issues (such as potential crashes, memory leaks, and other unsafe behavior) which aren't picked up by other tools (such as clang-tidy or cppcheck).
Currently, the tool reports around 1075 open issues when run on the QGIS master codebase.
These issues range from false positives to trivial fixes through to serious issues which require substantial work to fix. Unfortunately, the large number of trivial issues currently reported in QGIS make the tool effectively useless for QGIS, as the critical issues are hidden amongst the many hundreds of trivial issues.
This project describes a widespread cleanup to QGIS' Coverity Scan results
View the full QEP details here: https://github.com/qgis/QGIS-Enhancement-Proposals/blob/6587f46173c0f4bc7475b151bd1a26fb030f7a29/qep-337-coverity-scan-cleanup.md