> 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
Matthias Baesken has updated the pull request incrementally with one additional commit since the last revision: change description ------------- Changes: - all: https://git.openjdk.org/jdk/pull/26989/files - new: https://git.openjdk.org/jdk/pull/26989/files/8be68cb4..cf4cbe14 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=26989&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=26989&range=00-01 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 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
