walkero
/
cppcheck
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Manual: Improved information about bug hunting

This commit is contained in:
Daniel Marjamäki 2020-05-08 22:47:27 +02:00
parent 32cbbb09ed
commit 2c23a81470
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
man/manual.md
View File

@ -798,9 +798,11 @@ An example usage:
# Bug hunting # Bug hunting
If you want to detect more bugs and can accept false alarms then Cppcheck has analysis for that. If you want to detect most bugs and can accept false alarms then Cppcheck has analysis for that.
This analysis will be "soundy". The majority of the bugs should be detected however there is not a guarantee that Cppcheck will detect all bugs. This analysis is "soundy"; it should diagnose most bugs reported in CVEs and from dynamic analysis.
You have to expect false alarms. However Cppcheck tries to limit false alarms. The purpose of the data flow analysis is to limit false alarms.
Some possible use cases; Some possible use cases;
* you are writing new code and want to ensure it is safe. * you are writing new code and want to ensure it is safe.
@ -865,4 +867,3 @@ It is likely that you will get false alarms caused by incomplete data flow analy