Doomed program points
- First Online:
- Cite this article as:
- Hoenicke, J., Leino, K.R.M., Podelski, A. et al. Form Methods Syst Des (2010) 37: 171. doi:10.1007/s10703-010-0102-0
Any programming error that can be revealed before compiling a program saves precious time for the programmer. While integrated development environments already do a good job by detecting, e.g., data-flow abnormalities, current static analysis tools suffer from false positives (“noise”) or require strong user interaction.
We propose to avoid this deficiency by defining a new class of errors. A program fragment is doomed if its execution will inevitably fail, regardless of which state it is started in. We use a formal verification method to identify such errors fully automatically and, most significantly, without producing noise. We report on experiments with a prototype tool.
KeywordsReliability Program falsification Static checking
Unable to display preview. Download preview PDF.