Verification; Describe our philosophy in the manual

This commit is contained in:
Daniel Marjamäki 2020-01-01 09:39:57 +01:00
parent b44029cdaa
commit c6dfec5d5f
1 changed files with 13 additions and 0 deletions

View File

@ -722,6 +722,19 @@ Some possible use cases;
* you need extra help troubleshooting a crash or weird bug. * you need extra help troubleshooting a crash or weird bug.
* you tagged a release candidate and want to run extra analysis on that. * you tagged a release candidate and want to run extra analysis on that.
## Philosopphy
It is very important that we do warn about unsafe code. We want that users feel confident about the code we say is "safe".
However, a sloppy analysis that will report too much noise will not be useful. We need to have heuristics to avoid false positives.
At the moment there is no whole program analysis but that will be added later to avoid definite false positives.
The focus will be to detect "hidden" bugs. Good candidates are undefined behavior that does not cause a crash immediately but will just cause strange behavior.
* Buffer overflows
* Uninitialized variables
* Usage of dead pointers
## Compiling ## Compiling
make USE_Z3=yes make USE_Z3=yes