2013
DOI: 10.1007/978-3-319-03077-7_18
|View full text |Cite
|
Sign up to set email alerts
|

Domain Types: Abstract-Domain Selection Based on Variable Usage

Abstract: Abstract. The success of software model checking depends on finding an appropriate abstraction of the program to verify. The choice of the abstract domain and the analysis configuration is currently left to the user, who may not be familiar with the tradeoffs and performance details of the available abstract domains. We introduce the concept of domain types, which classify the program variables into types that are more fine-grained than standard declared types (e.g., 'int' and 'long') to guide the selection of… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
13
0

Year Published

2014
2014
2017
2017

Publication Types

Select...
6
1

Relationship

2
5

Authors

Journals

citations
Cited by 16 publications
(13 citation statements)
references
References 36 publications
0
13
0
Order By: Relevance
“…MUX treats the model checkers as black-boxes and derives a manyto-one selector. In order to obtain the best performance from available tools and strategies, white-box approaches aim at fine-tuning software verification tools [11,4] and some techniques try to derive tool chains of complementary tools [10,3]. Beyer et al [11] vary the precision of "merge" and other abstract operations to improve both scalability and precision of model checkers.…”
Section: Related Workmentioning
confidence: 99%
“…MUX treats the model checkers as black-boxes and derives a manyto-one selector. In order to obtain the best performance from available tools and strategies, white-box approaches aim at fine-tuning software verification tools [11,4] and some techniques try to derive tool chains of complementary tools [10,3]. Beyer et al [11] vary the precision of "merge" and other abstract operations to improve both scalability and precision of model checkers.…”
Section: Related Workmentioning
confidence: 99%
“…There, the explicit-state model checker SPIN has been used for reachability analysis, with a posteriori reasoning about test-case reuse among product variants, but without any reuse of reachability results among test goals. Applying CPAchecker for product-line verification has been proposed [3], incorporating BDD analysis for reuse of verification results [2]. Reuse of reachability analysis results for different test goals [7,8] has been presented and implemented as CPA/tiger on top of CPAchecker and corresponding reuse concepts have been applied to intermediate verification results [10].…”
Section: Related Workmentioning
confidence: 99%
“…Picking the right predicates, either upfront or dynamically during analysis [5], is essential in this setting to ensure rapid convergence of a model checker, and is in practice achieved through a combination of "systematic" methods (for CEGAR, in particular through Craig interpolation) and heuristics. For instance, SLAM extracts refinement predicates from counterexamples using domain-specific heuristics [16]; YOGI uses machine learning to choose the default set of heuristics for picking predicates [19]; CPAchecker uses domain types to decide whether to represent variables explicitly or using BDDs [2], and to choose refinement predicates [4]; and Eldarica uses heuristics to guide the process of Craig interpolation [18]. Similar heuristics can be identified in tools based on abstract interpretation, among others.…”
Section: Introductionmentioning
confidence: 99%