{"publication":"Formal Methods in System Design","month":"12","type":"journal_article","date_updated":"2025-09-30T09:48:58Z","publication_status":"published","user_id":"317138e5-6ab7-11ef-aa6d-ffef3953e345","issue":"2-3","author":[{"full_name":"Hoenicke, Jochen","last_name":"Hoenicke","first_name":"Jochen"},{"full_name":"Leino, Kari","first_name":"Kari","last_name":"Leino"},{"full_name":"Podelski, Andreas","last_name":"Podelski","first_name":"Andreas"},{"full_name":"Schäf, Martin","first_name":"Martin","last_name":"Schäf"},{"id":"447BFB88-F248-11E8-B48F-1D18A9856A87","last_name":"Wies","first_name":"Thomas","full_name":"Wies, Thomas"}],"quality_controlled":"1","_id":"533","publisher":"Springer","volume":37,"department":[{"_id":"ToHe"}],"publist_id":"7284","page":"171 - 199","language":[{"iso":"eng"}],"year":"2010","scopus_import":"1","status":"public","citation":{"mla":"Hoenicke, Jochen, et al. “Doomed Program Points.” Formal Methods in System Design, vol. 37, no. 2–3, Springer, 2010, pp. 171–99, doi:10.1007/s10703-010-0102-0.","ista":"Hoenicke J, Leino K, Podelski A, Schäf M, Wies T. 2010. Doomed program points. Formal Methods in System Design. 37(2–3), 171–199.","apa":"Hoenicke, J., Leino, K., Podelski, A., Schäf, M., & Wies, T. (2010). Doomed program points. Formal Methods in System Design. Springer. https://doi.org/10.1007/s10703-010-0102-0","ama":"Hoenicke J, Leino K, Podelski A, Schäf M, Wies T. Doomed program points. Formal Methods in System Design. 2010;37(2-3):171-199. doi:10.1007/s10703-010-0102-0","ieee":"J. Hoenicke, K. Leino, A. Podelski, M. Schäf, and T. Wies, “Doomed program points,” Formal Methods in System Design, vol. 37, no. 2–3. Springer, pp. 171–199, 2010.","chicago":"Hoenicke, Jochen, Kari Leino, Andreas Podelski, Martin Schäf, and Thomas Wies. “Doomed Program Points.” Formal Methods in System Design. Springer, 2010. https://doi.org/10.1007/s10703-010-0102-0.","short":"J. Hoenicke, K. Leino, A. Podelski, M. Schäf, T. Wies, Formal Methods in System Design 37 (2010) 171–199."},"corr_author":"1","day":"01","intvolume":" 37","title":"Doomed program points","abstract":[{"text":"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.","lang":"eng"}],"date_created":"2018-12-11T11:47:01Z","isi":1,"date_published":"2010-12-01T00:00:00Z","external_id":{"isi":["000286631700004"]},"doi":"10.1007/s10703-010-0102-0","oa_version":"None","article_processing_charge":"No"}