Thorough static analysis of device drivers

438 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Moving Fast with Software Verification (2015, methodology): “– Microsoft’s Static Driver Verifier [1] was one of the first automatic program verification tools to apply to real-world systems code.”
Debugging in the (very) large: ten years of implementation and experience (2009, methodology): “We continue to apply static analysis and model-checking tools to find errors early in the development process [ 2 , 3]. These tools are followed by extensive testing regimes before releasing software to users.”
Compositional shape analysis by means of bi-abduction (2009, methodology): “The last decade has seen a surge of interest in verification-by-static-analysis, with prominent success stories such as SLAM’s application of proof technology to Microsoft device drivers [Ball et al. 2006] and ASTRÉE’s proof of the absence of run-time errors in Airbus code [Cousot et al.”
S2E: a platform for in-vivo multi-path analysis of software systems (2011, methodology): “Most approaches abstract away the environment behind a model [2, 11], but writing abstract models is labor-intensive (taking in some cases multiple person-years [2]), they are rarely 100% accurate, and they”
Software model checking (2009, positive): “Slam was used successfully within Microsoft for device driver ver-iﬁcation [Ball et al. 2006] and developed into a commercial product (Static Driver Veriﬁer, SDV).”