should help you out It's possible you opted-out of the plugins when you were first installing Code::Blocks. If this is the case, you might need to install it manually. Under the "Plugins" menu, go to "Manage plugins..." and select "Install new." The plugin file is available here: http://www.2shared.com/file/-EZxdUJG/CppCheck-11.htm
Static code analysis WITH dynamic code analysis tools?
it fixes the issue It does make sense to combine both: you clearly want static analysis to detect real problems (not just plausible problems) and report them. For those places where the static analyzer is sure there is NOT a problem, nothing needs to be done or said. For those places where the static analyzer can't figure it out... you want dynamic analysis to watch for bad events at runtime. The basic answer is that tools that do static analysis are generally not well provisioned to instrument application codes, and those that instrument don't have lot of support for static analysis.
What are the tradeoffs of performing static analysis on source code, byte code, machine code, etc?
this one helps. What are the various tradeoffs for performing static analysis on various levels of code? For instance for Java, why would someone perform static analysis on Java source code vs. Java bytecode?
tool for Tcl code , to check code formatting and for static code analysis system