Suggesting edits to explain failing traces

    Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

    Abstract

    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.

    Original languageEnglish
    Title of host publicationLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
    PublisherSpringer Nature
    Pages287-293
    Number of pages7
    Volume9333
    ISBN (Print)9783319238197
    DOIs
    Publication statusPublished - 2015
    Event6th International Conference on Runtime Verification, RV 2015 - Vienna, Austria
    Duration: 22 Sept 201525 Sept 2015

    Publication series

    NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
    Volume9333
    ISSN (Print)03029743
    ISSN (Electronic)16113349

    Conference

    Conference6th International Conference on Runtime Verification, RV 2015
    Country/TerritoryAustria
    CityVienna
    Period22/09/1525/09/15

    Fingerprint

    Dive into the research topics of 'Suggesting edits to explain failing traces'. Together they form a unique fingerprint.

    Cite this