Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering 2008
DOI: 10.1145/1453101.1453131
|View full text |Cite
|
Sign up to set email alerts
|

Differential symbolic execution

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
197
0

Year Published

2011
2011
2014
2014

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 216 publications
(197 citation statements)
references
References 18 publications
0
197
0
Order By: Relevance
“…For example, the research community has invested a lot of effort in designing techniques for improving the testing of software patches, ranging from test suite prioritisation and selection algorithms [11,30,35] to program analysis techniques for test case generation and bug finding [1,2,20,21,27,28,36,40] to methods for surviving errors introduced by patches at runtime [14]. Many of these techniques depend on the existence of a manual test suite, sometimes requiring the availability of a test exercising the patch [24,37], sometimes making assumptions about the stability of program coverage or external behaviour over time [14,29], other times using it as a starting point for exploration [10,16,22,39], and often times employing it as a baseline for comparison [3,6,9,26].…”
Section: Introductionmentioning
confidence: 99%
“…For example, the research community has invested a lot of effort in designing techniques for improving the testing of software patches, ranging from test suite prioritisation and selection algorithms [11,30,35] to program analysis techniques for test case generation and bug finding [1,2,20,21,27,28,36,40] to methods for surviving errors introduced by patches at runtime [14]. Many of these techniques depend on the existence of a manual test suite, sometimes requiring the availability of a test exercising the patch [24,37], sometimes making assumptions about the stability of program coverage or external behaviour over time [14,29], other times using it as a starting point for exploration [10,16,22,39], and often times employing it as a baseline for comparison [3,6,9,26].…”
Section: Introductionmentioning
confidence: 99%
“…There are also approaches that attempt to show equivalence of the original and the upgraded software [14,10,7]. The SymDiff tool [10] decides conditional partial equivalence, i.e., equivalence under certain input constraints.…”
Section: Related Workmentioning
confidence: 99%
“…Moreover, SymDiff also allows automated extraction of the constraints and reports them to the user. The goal of differential symbolic execution [14] is to show equivalence of the two versions using symbolic execution. If the versions are not equivalent, a behavioral delta is constructed as a feedback for the user.…”
Section: Related Workmentioning
confidence: 99%
“…software patches. In particular, differential symbolic execution [23] for using symbolic execution to compute the behavioral characterization of a program change, and discusses several applications, including regression test generation. Xu and Rothermel [30] introduced directed test suite augmentation, in which existing test suites are combined with dynamic symbolic execution to execute uncovered branches in a patch.…”
Section: Related Workmentioning
confidence: 99%