1 / 9

The Software Model Checker B LAST

By D. Beyer et. al. The Software Model Checker B LAST. Presentation By: Pashootan Vaezipoor. Simon Fraser University (Spring 09). Introduction. Model Checking is a technique to verify a system desc against a spec Input: Program source (system desc) Temporal safty property (spec)

kimo
Download Presentation

The Software Model Checker B LAST

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. By D. Beyer et. al. The Software Model Checker BLAST Presentation By: Pashootan Vaezipoor Simon Fraser University (Spring 09)

  2. Introduction • Model Checking is a technique to verify a system desc against a spec • Input: • Program source (system desc) • Temporal safty property (spec) • Output: • Proof of correctness • Counterexample PresentationBy: Pashootan Vaezipoor Simon Fraser University (Spring 09)

  3. CEGAR • The paradigm behind some verification tools: • CounterExample Guided Abstraction Refinement

  4. BLAST • Software Model Checking • Checking Memory Safety • Generating Test PresentationBy: Pashootan Vaezipoor Simon Fraser University (Spring 09)

  5. BLAST (Software Model Checking) • Automatic Software Verification Tools: • Execution-based • Find bugs • Scale the search to large state spaces • Abstraction-based • Proving correctness • Improve precision • But CEGAR combines these two! • Automatic precision adjustment • Keeps the state space small PresentationBy: Pashootan Vaezipoor Simon Fraser University (Spring 09)

  6. BLAST (Memory Safety + Test Case) • Memory Safety • First we use CCURED to mark possible locations • Use Blast to eliminate unreachable error marks • Identify usage scenarios leading to errors • Test Case Generation • We need a spec or a set of coverage goals • Instead of the error path, BLAST creates a test vector • Test vector to the state q that always satisfies p • Test vector to the state q that never satisfies p • Test vector to the state q that smt satisfies p but smt not PresentationBy: Pashootan Vaezipoor Simon Fraser University (Spring 09)

  7. Example PresentationBy: Pashootan Vaezipoor Simon Fraser University (Spring 09)

  8. Example (CFA) PresentationBy: Pashootan Vaezipoor Simon Fraser University (Spring 09)

  9. PresentationBy: Pashootan Vaezipoor Simon Fraser University (Spring 09)

More Related