Diagnosing program errors with light-weighted specifications

Authors:
Rong Chen;Franz Wotawa
Affiliations:
College of Computer Science and Technology, Dalian Maritime University, Dalian, China;Institut for Software Technology, Technische Universität Graz, Graz, Austria
Venue:
IEA/AIE'06 Proceedings of the 19th international conference on Advances in Applied Artificial Intelligence: industrial, Engineering and Other Applications of Applied Intelligent Systems
Year:
2006

Citing 8
Cited 1

A theory of diagnosis from first principles

Artificial Intelligence
Aspect: detecting bugs with abstract dependences

ACM Transactions on Software Engineering and Methodology (TOSEM)
Using shape analysis to reduce finite-state models of concurrent Java programs

ACM Transactions on Software Engineering and Methodology (TOSEM)
A static analyzer for finding dynamic programming errors

Software—Practice & Experience
Simplifying and Isolating Failure-Inducing Input

IEEE Transactions on Software Engineering
From symptom to cause: localizing errors in counterexample traces

POPL '03 Proceedings of the 30th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
Automatic detection and repair of errors in data structures

OOPSLA '03 Proceedings of the 18th annual ACM SIGPLAN conference on Object-oriented programing, systems, languages, and applications
What went wrong: explaining counterexamples

SPIN'03 Proceedings of the 10th international conference on Model checking software

Model-based cognitive diagnosis of students' test performance in an e-learning environment

ICWL'10 Proceedings of the 2010 international conference on New horizons in web-based learning

Quantified Score

Hi-index	0.00

Visualization

Abstract

During the last decade many computer-aided debugging tools have been developed to assist users to detect program errors in a software system. A good example are model checking tools that provide counterexamples in case a given program violates the specified properties. However, even with a detailed erroneous run, it remains difficult for users to understand the error well and to isolate its root cause quickly and cheaply. This paper presents object store models for diagnosing program errors with light-weighted specifications. The models we use can keep track on object relations arising during program execution, detect counterexamples that violate user-provided properties, and highlight statements responsible for the violation. We have used the approach to help students to locate and correct the program errors in their course works.