Debugging object-oriented programs with behavior views

Authors:
Donglin Liang;Kai Xu
Affiliations:
University of Minnesota, Minneapolis, MN;University of Minnesota, Minneapolis, MN
Venue:
Proceedings of the sixth international symposium on Automated analysis-driven debugging
Year:
2005

Citing 7
Cited 0

A dataflow approach to event-based debugging

Software—Practice & Experience
Coca: an automated debugger for C

Proceedings of the 21st international conference on Software engineering
The unified software development process

The unified software development process
Extending and evaluating flow-insenstitive and context-insensitive points-to analyses for Java

PASTE '01 Proceedings of the 2001 ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
The Science of Debugging

The Science of Debugging
Two-Dimensional Pinpointing: Debugging with Normal Specifications

IEEE Software
An overview of JML tools and applications

International Journal on Software Tools for Technology Transfer (STTT) - Special section on formal methods for industrial critical systems

Quantified Score

Hi-index	0.00

Visualization

Abstract

A complex software system may perform many program tasks during execution to provide the required functionalities. To detect and localize bugs related to the implementation of these tasks, the software developers must be able to monitor the progress of the tasks during execution and check whether the actions for these tasks have been performed correctly. This paper presents a debugger to facilitate this monitoring. The debugger introduces a new kind of abstraction, the behavior views, that can be used to specify how the actions for a program task are expected to occur in various scenarios. Enhanced with statements that can check properties at various steps during the progress of the task, a behavior view can be used to monitor whether the actions for the tasks have been performed at the right time, on the right set of data, and with the right effects on the program states. Our initial case study indicates that the debugger can be useful for localizing bugs.