Error Reporting Logic

Authors:
C. Jaspan;T. Quan;J. Aldrich
Affiliations:
Carnegie Mellon Univ., Pittsburgh, PA;Carnegie Mellon Univ., Pittsburgh, PA;Carnegie Mellon Univ., Pittsburgh, PA
Venue:
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Year:
2008

Citing 9
Cited 1

A slicing-based approach for locating type errors

ACM Transactions on Software Engineering and Methodology (TOSEM)
Alloy: a lightweight object modelling notation

ACM Transactions on Software Engineering and Methodology (TOSEM)
Algorithmic program diagnosis

POPL '82 Proceedings of the 9th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
From symptom to cause: localizing errors in counterexample traces

POPL '03 Proceedings of the 30th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
Acme: an architecture description interchange language

CASCON '97 Proceedings of the 1997 conference of the Centre for Advanced Studies on Collaborative research
Type error slicing in implicitly typed higher-order languages

Science of Computer Programming - Special issue on 12th European symposium on programming (ESOP 2003)
Generating error traces from verification-condition counterexamples

Science of Computer Programming - Formal methods for components and objects pragmatic aspects and applications
Using SCL to Specify and Check Design Intent in Source Code

IEEE Transactions on Software Engineering
Searching for type-error messages

Proceedings of the 2007 ACM SIGPLAN conference on Programming language design and implementation

Automatic protocol-conformance recommendations

Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion

Quantified Score

Hi-index	0.00

Visualization

Abstract

When a system fails to meet its specification, it can be difficult to find the source of the error and determine how to fix it. In this paper, we introduce error reporting logic (ERL), an algorithm and tool that produces succinct explanations for why a target system violates a specification expressed in first order predicate logic. ERL analyzes the specification to determine which parts contributed to the failure, and it displays an error message specific to those parts. Additionally, ERL uses a heuristic to determine which object in the target system is responsible for the error. Results from a small user study suggest that the combination of a more focused error message and a responsible object for the error helps users to find the failure in the system more effectively. The study also yielded insights into how the users find and fix errors that may guide future research.