ACM Home Page
Please provide us with feedback. Feedback
Isolating relevant component interactions with JINSI
Full text PdfPdf (340 KB)
Source International Conference on Software Engineering archive
Proceedings of the 2006 international workshop on Dynamic systems analysis table of contents
Shanghai, China
SESSION: Testing and debugging table of contents
Pages: 3 - 10  
Year of Publication: 2006
ISBN:1-59593-400-6
Authors
Alessandro Orso  Georgia Institute of Technology
Shrinivas Joshi  Georgia Institute of Technology
Martin Burger  Saarland University
Andreas Zeller  Saarland University
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 1,   Downloads (12 Months): 12,   Citation Count: 6
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1138912.1138915
What is a DOI?

ABSTRACT

When a component in a large system fails, developers encounter two problems: (1) reproducing the failure, and (2) investigating the causes of such a failure. Our JINSI tool lets developers capture and replay the interactions between a component and its environment, thus allowing for reproducing the failure at will. In addition, JINSI uses delta debugging to automatically isolate the subset of the interactions that is relevant for the failure. In a first study, JINSI has successfully isolated the relevant interaction of a JAVA component: "Out of the 32 interactions with the <VendingMachine> (BOB - wasn't sure about this one)component, seven interactions suffice to produce the failure.


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
Byte-Code Engineering Library (BCEL). http://jakarta.apache.org/bcel/.
 
2
EasyMock home page. http://www.easymock.org/.
 
3
Javassist home page. http://www.csg.is.titech.ac.jp/~chiba/javassist/.
 
4
 
5
B. Lewis. Debugging backwards in time. In M. Ronsse, editor, Proc. Fifth Int. Workshop on Automated and Algorithmic Debugging (AADEBUG), Sept. 2003.
6
7
8
 
9
 
10

CITED BY  6

Collaborative Colleagues:
Alessandro Orso: colleagues
Shrinivas Joshi: colleagues
Martin Burger: colleagues
Andreas Zeller: colleagues