2017
DOI: 10.1007/978-3-662-54577-5_17
|View full text |Cite
|
Sign up to set email alerts
|

Connecting Program Synthesis and Reachability: Automatic Program Repair Using Test-Input Generation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
6
0

Year Published

2017
2017
2022
2022

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 14 publications
(7 citation statements)
references
References 42 publications
0
6
0
Order By: Relevance
“…Both of these target normal testing rather than synthesis. Nguyen et al [19] leverage symbolic execution over input-output test pairs to perform program repair. However, they use these tests to model individual expressions instead of modeling entire functions.…”
Section: Related Workmentioning
confidence: 99%
“…Both of these target normal testing rather than synthesis. Nguyen et al [19] leverage symbolic execution over input-output test pairs to perform program repair. However, they use these tests to model individual expressions instead of modeling entire functions.…”
Section: Related Workmentioning
confidence: 99%
“…In the literature there is also a wide range of techniques for automated program repair using formal methods [4,10,19,22,29,32,33,42]. Both [11] and [37] also use fault localization followed by applying mutations for repair.…”
Section: Related Workmentioning
confidence: 99%
“…Start is non-deterministic; it contains four calls to an external function nd(), which returns a non-deterministically chosen Boolean value. The calls to nd() can be understood as controlling whether or not a production is selected from G 2 during a top-down, left-to-right generation of an expression-tree: lines (3)-( 8) correspond to "Start ::= Plus(Start, Start)," and lines (10), (11), (12), and (13) correspond to "Start ::= x," "Start ::= y," "Start ::= 1," and "Start ::= 0," respectively. The code in the five cases in the body of Start encodes the semantics of the respective production of G 2 ; in particular, the statements that are executed along any execution path of P [G 2 , E 1 ] implement the bottom-up evaluation of some expression-tree that can be generated by G 2 .…”
Section: Illustrative Examplementioning
confidence: 99%
“…Synthesis as Reachability. CETI [12] introduces a technique for encoding template-based synthesis problems as reachability problems. The CETI encoding only applies to the specific setting in which (i) the search space is described by an imperative program with a finite number of holes-i.e., the values that the synthesizer has to discover-and (ii) the specification is given as a finite number of input-output test cases with which the target program should agree.…”
Section: Related Workmentioning
confidence: 99%