The SLAM project: debugging system software via static analysis

DMCA

The SLAM project: debugging system software via static analysis

Cached

Download Links

Other Repositories/Bibliography

DBLP

by Thomas Ball , Sriram K. Rajamani

Venue:	SIGPLAN Not
Citations:	472 - 17 self

BibTeX

@ARTICLE{Ball_theslam,
    author = {Thomas Ball and Sriram K. Rajamani},
    title = {The SLAM project: debugging system software via static analysis},
    journal = {SIGPLAN Not},
    year = {},
    pages = {2002}
}

OpenURL

Abstract

Abstract. The goal of the SLAM project is to check whether or not a program obeys "API usage rules " that specif[y what it means to be a good client of an API. The SLAM toolkit statically analyzes a C program to determine whether or not it violates given usage rules. The toolkit has two unique aspects: it does not require the programmer to annotate the source program (invariants are inferred); it minimizes noise (false error messages) through a process known as "counterexample-driven refinement". SLAM exploits and extends results fi'om program analysis, model checking and automated deduction.}V ~ have successfully applied the SLAM toolkit to Windows XP device drivers, to both validate behavior and find defects in their usage of kernel APIs. Context. Today, many programmers are realizing the benefits of using languages with static type systems. By providing

Keyphrases

slam project static analysis debugging system software slam toolkit slam exploit om program analysis window xp device driver usage rule good client counterexample-driven refinement static type system automated deduction program obeys api usage rule model checking source program unique aspect many programmer validate behavior kernel apis false error message

DMCA