ACM Home Page
Please provide us with feedback. Feedback
Using redundancies to find errors
Full text pdf formatPdf (266 KB)
Source Foundations of Software Engineering archive
Proceedings of the 10th ACM SIGSOFT symposium on Foundations of software engineering table of contents
Charleston, South Carolina, USA
SESSION: Static program analysis table of contents
Pages: 51 - 60  
Year of Publication: 2002
ISBN:1-58113-514-9
Authors
Yichen Xie  Stanford University, Stanford, CA
Dawson Engler  Stanford University, Stanford, CA
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 34,   Citation Count: 8
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/587051.587060
What is a DOI?

ABSTRACT

This paper explores the idea that redundant operations, like type errors, commonly flag correctness errors. We experimentally test this idea by writing and applying four redundancy checkers to the Linux operating system, finding many errors. We then use these errors to demonstrate that redundancies, even when harmless, strongly correlate with the presence of traditional hard errors (e.g., null pointer dereferences, unreleased locks). Finally we show that how flagging redundant operations gives a way to make specifications "fail stop" bydetecting dangerous omissions.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
 
4
 
5
 
6
G. Casella and R. L. Berger. Statistical Inference. Wadsworth Group, Pacific Grove, CA, 2002.
 
7
8
9
 
10
D. L. Detlefs. An overview of the extended static checking system. In Proceedings of the First Workshop on Formal Methods in Software Practice, pages 1--9, January 1996.
11
12
 
13
14
 
15
D. Freedman, R. Pisani, and R. Purves. Statistics. W.W. Norton, third edition edition, 1998.
16
 
17
J. C. Huang. Detection of data flow anomaly through program instrumentation. IEEE Transactions on Software Engineering, 5(3):226--236, May 1979.
 
18
L. J. Osterweil and L. D. Fosdick. Dave--a validation error detection and documentation system for fortran programs. Software: Practice and Experience, 6(4):473--486, December 1976.
19
 
20
N. Sterling. WARLOCK - a static data race analysis tool. In USENIX Winter, pages 97--106, 1993.
 
21
D. Wagner, J. Foster, E. Brewer, and A. Aiken. A first step towards automated detection of buffer overrun vulnerabilities. In The 2000 Network and Distributed Systems Security Conference. San Diego, CA, February 2000.

CITED BY  8
 
 

Collaborative Colleagues:
Yichen Xie: colleagues
Dawson Engler: colleagues

Peer to Peer - Readers of this Article have also read: