Replaying and isolating failing multi-object interactions

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Replaying and isolating failing multi-object interactions

Full text

Pdf (1.47 MB)

Source

International Symposium on Software Testing and Analysis archive
Proceedings of the 2008 international workshop on dynamic analysis: held in conjunction with the ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA 2008) table of contents

Seattle, Washington

SESSION: Fault localization table of contents

Pages 71-77

Year of Publication: 2008

ISBN:978-1-60558-054-8

Authors

Martin Burger	Saarland University, Saarbrücken, Germany
Andreas Zeller	Saarland University, Saarbrücken, Germany

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 9, Downloads (12 Months): 51, Citation Count: 1

Additional Information:

abstract references cited by index terms collaborative colleagues

Tools and Actions:	Request Permissions 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/1401827.1401842 What is a DOI?

ABSTRACT

When a program fails, there are typically multiple objects that contribute to the failure. Our JINSI tool automatically captures the failure-causing interaction between objects and isolates a sequence of calls that all are relevant for reproducing the failure. In contrast to existing work, JINSI also isolates relevant interaction within the observed component and thus across all layers of a complex application. In a proof of concept, JINSI has successfully isolated the interaction for a failure of the COLUMBA e-mail client, pinpointing the defect: "Out of the 187,532 interactions in the addressbook component, two incoming calls suffice to reproduce 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	Shay Artzi , Sunghun Kim , Michael D. Ernst, ReCrash: Making Software Failures Reproducible by Preserving Object States, Proceedings of the 22nd European conference on Object-Oriented Programming, July 07-11, 2008, Paphos, Cypress [doi>10.1007/978-3-540-70592-5_23]
	2	Holger Cleve , Andreas Zeller, Locating causes of program failures, Proceedings of the 27th international conference on Software engineering, May 15-21, 2005, St. Louis, MO, USA [doi>10.1145/1062455.1062522]
	3	Valentin Dallmeier , Thomas Zimmermann, Extraction of bug localization benchmarks from history, Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering, November 05-09, 2007, Atlanta, Georgia, USA [doi>10.1145/1321631.1321702]
	4	Javassist home page. http://www.csg.is.titech.ac.jp/~chiba/javassist/.
	5	James A. Jones , Mary Jean Harrold , John Stasko, Visualization of test information to assist fault localization, Proceedings of the 24th International Conference on Software Engineering, May 19-25, 2002, Orlando, Florida [doi>10.1145/581339.581397]
	6	Yong Lei , James H. Andrews, Minimization of Randomized Unit Test Cases, Proceedings of the 16th IEEE International Symposium on Software Reliability Engineering, p.267-276, November 08-11, 2005 [doi>10.1109/ISSRE.2005.28]
	7	Andreas Leitner , Manuel Oriol , Andreas Zeller , Ilinca Ciupa , Bertrand Meyer, Efficient unit test case minimization, Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering, November 05-09, 2007, Atlanta, Georgia, USA [doi>10.1145/1321631.1321698]
	8	B. Lewis. Debugging backwards in time. In M. Ronsse, editor, Proc. Fifth Int. Workshop on Automated and Algorithmic Debugging (AADEBUG), Sept. 2003.
	9	S. Neuhaus and A. Zeller. Isolating cause-effect chains in computer systems. In Software Engineering, volume 105 of LNI, pages 169--180. GI, 2007.
	10	Alessandro Orso , Shrinivas Joshi , Martin Burger , Andreas Zeller, Isolating relevant component interactions with JINSI, Proceedings of the 2006 international workshop on Dynamic systems analysis, May 23-23, 2006, Shanghai, China [doi>10.1145/1138912.1138915]
	11	Alessandro Orso , Bryan Kennedy, Selective capture and replay of program executions, Proceedings of the third international workshop on Dynamic analysis, p.1-7, May 17-17, 2005, St. Louis, Missouri
	12	Atanas Rountev, Precise Identification of Side-Effect-Free Methods in Java, Proceedings of the 20th IEEE International Conference on Software Maintenance, p.82-91, September 11-14, 2004
	13	David Saff , Shay Artzi , Jeff H. Perkins , Michael D. Ernst, Automatic test factoring for java, Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering, November 07-11, 2005, Long Beach, CA, USA [doi>10.1145/1101908.1101927]
	14	F. Tip. A Survey of Program Slicing Techniques. Centrum voor Wiskunde en Informatica, 1994.
	15	Andreas Zeller, Why Programs Fail: A Guide to Systematic Debugging, Morgan Kaufmann Publishers Inc., San Francisco, CA, 2005
	16	Andreas Zeller , Ralf Hildebrandt, Simplifying and Isolating Failure-Inducing Input, IEEE Transactions on Software Engineering, v.28 n.2, p.183-200, February 2002 [doi>10.1109/32.988498]
	17	Andreas Zeller , Dorothea Lütkehaus, DDD—a free graphical front-end for UNIX debuggers, ACM SIGPLAN Notices, v.31 n.1, p.22-27, Jan. 1996 [doi>10.1145/249094.249108]