<div dir="ltr">Hi<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 18, 2013 at 4:39 AM, Maciek Borzecki <span dir="ltr"></span>wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Have you been able to compare cppcheck with clang's static-analyzer?<br>
Both issues that you managed to identify should have been found by<br>
clang as well.<br></blockquote><div><br></div><div>clang and cppcheck has some overlap but sometimes finds issues that the other doesn't. Ideally you want to run them both before each release. You could even do a GCC build with more warnings enabled to go the extra mile. The latest version of GCC with -Wall -Wextra -std=c99 seems pretty similar to Clang. <br>
<br><a href="http://gcc.gnu.org/wiki/ClangDiagnosticsComparison">http://gcc.gnu.org/wiki/ClangDiagnosticsComparison</a><br><br>I also checked out splint but it returns too many false positives to be really useful. The only thing I haven't personally looked at is Coverity. <br>
<br></div><div>Rahul<br></div></div></div></div></div>