Learning the language of error

Martin Chapman, Hana Chockler, Pascal Kesseli, Daniel Kroening, Ofer Strichman, Michael Tautschnig

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

Abstract

We propose to harness Angluin’s L∗ algorithm for learning a deterministic finite automaton that describes the possible scenarios under which a given program error occurs. The alphabet of this automaton is given by the user (for instance, a subset of the function call sites or branches), and hence the automaton describes a user-defined abstraction of those scenarios. More generally, the same technique can be used for visualising the behavior of a program or parts thereof. This can be used, for example, for visually comparing different versions of a program, by presenting an automaton for the behavior in the symmetric difference between them, or for assisting in merging several development branches. We present initial experiments that demonstrate the power of an abstract visual representation of errors and of program segments.

Original languageEnglish
Title of host publicationAutomated Technology for Verification and Analysis - 13th International Symposium, ATVA 2015, Proceedings
EditorsBernd Finkbeiner, Geguang Pu, Lijun Zhang
Pages114-130
Number of pages17
DOIs
StatePublished - 2015
Event13th International Symposium on Automated Technology for Verification and Analysis, ATVA 2015 - Shanghai, China
Duration: 12 Oct 201515 Oct 2015

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume9364

Conference

Conference13th International Symposium on Automated Technology for Verification and Analysis, ATVA 2015
Country/TerritoryChina
CityShanghai
Period12/10/1515/10/15

All Science Journal Classification (ASJC) codes

  • Theoretical Computer Science
  • General Computer Science

Fingerprint

Dive into the research topics of 'Learning the language of error'. Together they form a unique fingerprint.

Cite this