How to deal with static analysis findings: MISRA
summary
Practical rules for handling static analysis findings; concrete steps: require a file and line, explain what the issue is and why it matters, link standards or tests, and offer an automatic fix or a reproducible test. Focus is MISRA C++ violations and the free MISRA Compliance document that defines how to justify deviations. Track true/false positives and negatives, add a consented deviation process, and consider tool qualification when findings are missing.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:59Static analysis findings
- 19:12What is MISRA
- 28:54MISRA document structure
- 35:16MISRA compliance and deviations
- 43:26MISRA rule violations
- 49:26Best practices for developers
- 51:41Q&A
related talks
01h 20mSafer C++: MISRA-C++ : 202X Rules and Beyond
58mMisra Parallelism Safety-critical Guidelines for C++11, 17, Then C++20, 23
01h 05mSafer C++ with MISRA-C++ 2023
57mThe Misra C++:2023 Guidelines
19mWhy AI Code Passes OWASP but Fails MISRA
58mSecurity Static Analysis - Avoiding an Angry Mob of Engineers
01h 35mSafety and Security for C++: Panel Discussion
01h 29mC++ Safety And Security Panel 2024