Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering 2013
DOI: 10.1145/2491411.2491448
|View full text |Cite
|
Sign up to set email alerts
|

Explaining inconsistent code

Abstract: A code fragment is inconsistent if it is not part of any normally terminating execution. Examples of such inconsistencies include code that is unreachable, code that always fails due to a run-time error, and code that makes conflicting assumptions about the program state. In this paper, we consider the problem of automatically explaining inconsistent code. This problem is difficult because traditional fault localization techniques do not apply. Our solution relies on a novel algorithm that takes an infeasible … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
8
0

Year Published

2014
2014
2020
2020

Publication Types

Select...
5
1
1

Relationship

1
6

Authors

Journals

citations
Cited by 15 publications
(8 citation statements)
references
References 38 publications
0
8
0
Order By: Relevance
“…The use of error invariants [7,13,18,29] is a closely-related fault-localization technique. Error invariants are computed from Craig interpolants along an error trace and capture which states will produce the error from that point on.…”
Section: Related Workmentioning
confidence: 99%
“…The use of error invariants [7,13,18,29] is a closely-related fault-localization technique. Error invariants are computed from Craig interpolants along an error trace and capture which states will produce the error from that point on.…”
Section: Related Workmentioning
confidence: 99%
“…Since a flow-sensitive TF represents itself more information, it is larger and more complex than a flow-insensitive TF. Furthermore, as in flow-insensitive TF, it is necessary to construct many TF in order to deal with independent faults because the flow-sensitive TF does not encode all execution paths [23]. Concerning data flowdependent faults, they can be identified with both flow-insensitive and flow-sensitive TF.…”
Section: Importance Of Trace Formulasmentioning
confidence: 99%
“…FBFL techniques represent an error trace using an SMT formula and analyze it to find suspicious locations. These techniques include using error invariants [6,14,17,40], maximum satisfiability [21,24,25], and weakest preconditions [7]. What we were able to show in this paper, is that the methods of [6,14,21] are not must.…”
Section: Related Workmentioning
confidence: 72%
“…Other approaches for fault localization include spectrum-based (SBFL) [1,13,20,31,44], mutation-based (MBFL) [15,18,30,35] and formula-based (FBFL) [7,14,17,21,40]. Both SBFL and MBFL techniques compute the suspiciousness of a statement using coverage information from failing and passing test executions.…”
Section: Related Workmentioning
confidence: 99%