TY - GEN
T1 - Suggesting edits to explain failing traces
AU - Reger, Giles
PY - 2015
Y1 - 2015
N2 - Runtime verification involves checking whether an execution trace produced by a running system satisfies a specification. However, a simple ‘yes’ or ‘no’ answer may not be sufficient; often we need to understand why a violation occurs. This paper considers how computing the edit-distance between a trace and a specification can explain violations by suggesting correcting edits to the trace. By including information about the code location producing events in the trace, this method can highlight sources of bugs and suggest potential fixes.
AB - Runtime verification involves checking whether an execution trace produced by a running system satisfies a specification. However, a simple ‘yes’ or ‘no’ answer may not be sufficient; often we need to understand why a violation occurs. This paper considers how computing the edit-distance between a trace and a specification can explain violations by suggesting correcting edits to the trace. By including information about the code location producing events in the trace, this method can highlight sources of bugs and suggest potential fixes.
UR - http://www.scopus.com/inward/record.url?scp=84950323166&partnerID=8YFLogxK
U2 - 10.1007/978-3-319-23820-3_20
DO - 10.1007/978-3-319-23820-3_20
M3 - Conference contribution
AN - SCOPUS:84950323166
SN - 9783319238197
VL - 9333
T3 - Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
SP - 287
EP - 293
BT - Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
PB - Springer Nature
T2 - 6th International Conference on Runtime Verification, RV 2015
Y2 - 22 September 2015 through 25 September 2015
ER -