Recent versions of GCC have a static code analyzer option (-fanalyzer) that works quite well for C code (but it has still issues with C++). This can be used to identify e.g. some leaks like memory leaks, double close, use of uninitialized data etc. . Some info about it :
https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html https://developers.redhat.com/articles/2023/05/31/improvements-static-analysis-gcc-13-compiler ------------- Commit messages: - JDK-8362516 Changes: https://git.openjdk.org/jdk/pull/26989/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=26989&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8362516 Stats: 28 lines in 2 files changed: 28 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/26989.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/26989/head:pull/26989 PR: https://git.openjdk.org/jdk/pull/26989
