Add Clang Static Analyzer (scan-build) CI Integration
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 455
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Required prerequisites
- Search the issue tracker to check if your feature has already been mentioned or rejected in other issues.
Describe the feature
Related to #3757. As noted in #3748 and #3711 we have caught quite a few latent bugs (Also #3752 and #3755) in development of MacOS support that might have been caught by a static analysis tool like scan-build. This can help catching null pointer derefs, resources leaks, logic errors, etc. early. It will catch a different set of errors than ASAN.
We would add this as a separate CI job. Similar to ASAN it can be slow and we should consider how it fits in the overall CI pipeline. We will likely have to exclude third party code.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing ASAN CI job and the scan-build command-line documentation linked in the issue. Define a separate CI job that excludes third-party code where needed, then confirm that it runs successfully and fits the overall CI pipeline without duplicating ASAN coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100