|Version 48 (modified by hyd_danmar, 4 years ago)|
This wiki is about Cppcheck development
For developers and testers the --debug-warnings can be used. It warns about unhandled code, bailouts, etc.
To see extensive debug output use --debug. This is most useful on small code samples because it is verbose.
Creating new tickets
- false positive (when --all is not used)
- hang / crash
- fail to compile
- new checks
- an existing check fails to detect bug (use the component "improve check")
- false positive (when --all is used)
- suggestions about different output
- Latest version can be found in the git
git clone git://github.com/danmar/cppcheck.git
Simple issues to fix
If you want to help us you can start by looking at the tickets that we consider to be simple. http://sourceforge.net/apps/trac/cppcheck/query?status=new&col=id&col=summary&keywords=~simple
How to submit a patch
Create a ticket that describes the problem. Then add your patch as a file attachment.
Version 1.45 is planned to be released on September 11th.
Cppcheck is basically a pattern matcher. The input code will be matched against various patterns that are known to be bugs.
Analyzing a file is made in 3 steps:
- Run all checks - pattern matching of the tokens