Declarative and visual debugging in Eclipse

ABSTRACT

We present a declarative and visual debugging environment for Eclipse called JIVE.¹ Traditional debugging is procedural in that a programmer must proceed step-by-step and object-by-object in order to uncover the cause of an error. In contrast, we present a declarative approach to debugging consisting of a flexible set of queries over a program's execution history as well as over individual runtime states. This runtime information is depicted in a visual manner during program execution in order to aid the debugging process. The current state of execution is depicted through an enhanced object diagram, and the history of execution is depicted by a sequence diagram. Our methodology makes use of these diagrams as a means of formulating queries and reporting results in a visual manner. It also supports revisiting past runtime states, either through reverse stepping of the program or through queries that report information from past states. Eclipse serves as an ideal framework for implementing JIVE since, like the JIVE architecture, it makes crucial use of the Java Platform Debugging Architecture (JPDA). This paper presents details of the JIVE architecture and its integration into Eclipse.

REFERENCES

• 1: Hiralal Agrawal , Richard A. Demillo , Eugene H. Spafford, Debugging with dynamic slicing and backtracking, Software—Practice & Experience, v.23 n.6, p.589-616, June 1993 [doi>10.1002/spe.4380230603]
• 2: Wim De Pauw , David Lorenz , John Vlissides , Mark Wegman, Execution patterns in object-oriented visualization, Proceedings of the 4th conference on USENIX Conference on Object-Oriented Technologies and Systems, p.16-16, April 27-30, 1998, Santa Fe, New Mexico
• 3: Wim De Pauw , John M. Vlissides, Visualizing Object-Oriented Programs with Jinsight, Workshop ion on Object-Oriented Technology, p.541-542, July 20-24, 1998
• 4: M. Ducassé. Opium: An extendable trace analyser for Prolog. The Journal of Logic Programming, 1999.
• 5: Paul V. Gestwicki , Bharat Jayaraman, Interactive visualization of object-oriented programs, State University of New York at Buffalo, Buffalo, NY, 2005
• 6: Paul Gestwicki , Bharat Jayaraman, Interactive Visualization of Java Programs, Proceedings of the IEEE 2002 Symposia on Human Centric Computing Languages and Environments (HCC'02), p.226, September 03-06, 2002
• 7: Paul Gestwicki , Bharat Jayaraman, Methodology and architecture of JIVE, Proceedings of the 2005 ACM symposium on Software visualization, May 14-15, 2005, St. Louis, Missouri [doi>10.1145/1056018.1056032]
• 8: Hani Z. Girgis , Bharat Jayaraman , Paul V. Gestwicki, Visualizing errors in object oriented programs, Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications, October 16-20, 2005, San Diego, CA, USA [doi>10.1145/1094855.1094911]
• 9: Simon F. Goldsmith , Robert O'Callahan , Alex Aiken, Relational queries over program traces, Proceedings of the 20th annual ACM SIGPLAN conference on Object oriented programming, systems, languages, and applications, October 16-20, 2005, San Diego, CA, USA
• 10: Andrew J. Ko , Brad A. Myers, Designing the whyline: a debugging interface for asking questions about program behavior, Proceedings of the SIGCHI conference on Human factors in computing systems, p.151-158, April 24-29, 2004, Vienna, Austria [doi>10.1145/985692.985712]
• 11: Michael Kölling , John Rosenberg, Guidelines for teaching object orientation with Java, ACM SIGCSE Bulletin, v.33 n.3, p.33-36, Sept. 2001
• 12: Ralf Kollmann , Martin Gogolla, Capturing Dynamic Program Behavior with UML Collaboration Diagrams, Proceedings of the Fifth European Conference on Software Maintenance and Reengineering, p.58, March 14-16, 2001
• 13: Raimondas Lencevicius , Urs Hölzle , Ambuj K. Singh, Query-based debugging of object-oriented programs, Proceedings of the 12th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications, p.304-317, October 05-09, 1997, Atlanta, Georgia, United States
• 14: B. Lewis. Debugging backwards in time. In ArXiv Computer Science, pages 225--235, 2003.
• 15: Michael Martin , Benjamin Livshits , Monica S. Lam, Finding application errors and security flaws using PQL: a program query language, Proceedings of the 20th annual ACM SIGPLAN conference on Object oriented programming, systems, languages, and applications, October 16-20, 2005, San Diego, CA, USA
• 16: National Institute of Standards and Technology (NIST). The economic impacts of inadequate infrastructure for software testing. Technical Report 02--3, May 2002.
• 17: Rainer Oechsle , Thomas Schmitt, JAVAVIS: Automatic Program Visualization with Object and Sequence Diagrams Using the Java Debug Interface (JDI), Revised Lectures on Software Visualization, International Seminar, p.176-190, May 20-25, 2001
• 18: Steven P. Reiss, Visualizing Java in action, Proceedings of the 2003 ACM symposium on Software visualization, June 11-13, 2003, San Diego, California [doi>10.1145/774833.774842]
• 19: R. Sharp , A. Rountev, Interactive Exploration of UML Sequence Diagrams, Proceedings of the 3rd IEEE International Workshop on Visualizing Software for Understanding and Analysis, p.8, September 25-25, 2005 [doi>10.1109/VISSOF.2005.1684295]
• 20: Tarja Systä , Kai Koskimies , Hausi Müller, Shimba—an environment for reverse engineering Java software systems, Software—Practice & Experience, v.31 n.4, p.371-394, April 10, 2001 [doi>10.1002/spe.386]
• 21: The Eclipse Foundation. Eclipse Platform. http://www.eclipse.org/.
• 22: 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]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.5 Testing and Debugging

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.6 Programming Environments