2006
DOI: 10.1007/11817963_28
|View full text |Cite
|
Sign up to set email alerts
|

Symbolic Model Checking of Concurrent Programs Using Partial Orders and On-the-Fly Transactions

Abstract: Abstract. The state explosion problem is one of the core bottlenecks in the model checking of concurrent software. We show how to ameliorate the problem by combining the ability of partial order techniques to reduce the state space of the concurrent program with the power of symbolic model checking to explore large state spaces. Our new verification methodology involves translating the given concurrent program into a circuit-based model which gives us the flexibility to then employ any model checking technique… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
40
0

Year Published

2011
2011
2017
2017

Publication Types

Select...
6

Relationship

1
5

Authors

Journals

citations
Cited by 23 publications
(40 citation statements)
references
References 19 publications
0
40
0
Order By: Relevance
“…There have been some efforts [13][14][15][16] to combine symbolic model checking with the above mentioned state-reduction methods for verifying concurrent software. However, they still suffer from lack of scalability.…”
Section: Related Workmentioning
confidence: 99%
See 4 more Smart Citations
“…There have been some efforts [13][14][15][16] to combine symbolic model checking with the above mentioned state-reduction methods for verifying concurrent software. However, they still suffer from lack of scalability.…”
Section: Related Workmentioning
confidence: 99%
“…We have implemented our techniques in a prototype SMT-based BMC framework, and demonstrate its effectiveness through controlled experiments on a complex concurrency benchmark. For experiments, we contrast our lazy modeling approach with an eager modeling [13][14][15][16] of the concurrent system, i.e., a monolithic model synchronously composed with interleaving semantics (and possibly, with state-reduction constraints) enforced by an explicit scheduler, capturing all concurrent behaviors of the system eagerly.…”
Section: Our Approach: Overviewmentioning
confidence: 99%
See 3 more Smart Citations