Go to file
Michael Tautschnig e832e5409f Support va_list types defined via one-element arrays
Some SV-COMP device driver benchmarks define a va_list type as in the
included regression test. As one-element arrays shouldn't make a
substantial difference we can easily support this case.
2019-05-28 10:57:35 +00:00
.githooks Make the pre-commit hook report non-temporary path names (#477) 2017-02-02 20:39:09 +00:00
.github Include User Guide item in pull request template 2018-11-15 19:23:58 +00:00
cmake Add DownloadProject cmake script 2017-09-27 11:22:20 +01:00
doc Move printf to C library and support return values 2019-05-21 16:06:56 +01:00
integration/xen Fix Xen integration test 2019-03-06 22:34:06 +00:00
jbmc fix result type of aaload 2019-05-27 19:54:59 +01:00
pkg/arch Add CBMC package build file for Arch Linux 2017-04-26 16:29:00 +01:00
regression Support va_list types defined via one-element arrays 2019-05-28 10:57:35 +00:00
scripts Add check for missing unidiff dependency 2019-04-11 15:11:56 +01:00
src Support va_list types defined via one-element arrays 2019-05-28 10:57:35 +00:00
unit Return reference from methods that cannot return a nullpointer 2019-05-23 14:26:14 +01:00
.clang-format Make clang-format indent nested preprocessor directives 2019-03-30 12:50:59 +00:00
.clang-format-ignore Use .clang-format-ignore 2019-01-29 09:43:59 +00:00
.dir-locals.el Move Emacs style file so it affects unit tests as well as main source 2017-08-16 12:43:32 +01:00
.editorconfig Don't remove trailing spaces from patch files 2016-11-29 17:26:59 +00:00
.gitattributes added test.desc as text 2016-08-15 12:35:10 +01:00
.gitignore Add function harness generator and generator factory 2019-02-07 16:44:02 +00:00
.gitmodules Use submodule to download java-models-library 2018-07-09 21:13:37 +01:00
.travis.yml Make memory analyzer optional 2019-05-16 11:56:04 +01:00
CHANGELOG Add new goto-instrument option print-global-state-size 2018-06-20 09:38:30 +01:00
CMakeLists.txt Make memory analyzer optional 2019-05-16 11:56:04 +01:00
CODEOWNERS CODEOWNERS: C. Smowton in goto-symex and goto-instrument 2019-03-01 14:41:12 +00:00
CODING_STANDARD.md Update coding standard for function brief documentation 2019-05-09 17:53:56 +01:00
COMPILING.md Make JBMC build optional with cmake 2019-03-14 07:05:57 -07:00
LICENSE update year 2016-09-05 17:05:55 +01:00
MINI-PROJECTS.md Add CBMC Mini Projects list 2019-02-06 21:23:30 +00:00
README.md Update Codebuild badge 2019-03-25 12:07:51 +00:00
buildspec-linux-clang.yml Suppress color output on AWS CodeBuild 2019-05-10 18:43:47 +01:00
buildspec-linux-cmake-gcc.yml Suppress color output on AWS CodeBuild 2019-05-10 18:43:47 +01:00
buildspec-windows.yml Suppress color output on AWS CodeBuild 2019-05-10 18:43:47 +01:00
buildspec.yml Suppress color output on AWS CodeBuild 2019-05-10 18:43:47 +01:00
gcloud-travis-cbmc.json.enc Add encrypted GCloud key for Travis 2018-03-20 12:16:01 +00:00

README.md

Build Status Build Status Build Status Build Status

CProver Wiki

CProver Documentation

About

CBMC is a Bounded Model Checker for C and C++ programs. It supports C89, C99, most of C11 and most compiler extensions provided by gcc and Visual Studio. It also supports SystemC using Scoot. It allows verifying array bounds (buffer overflows), pointer safety, exceptions and user-specified assertions. Furthermore, it can check C and C++ for consistency with other languages, such as Verilog. The verification is performed by unwinding the loops in the program and passing the resulting equation to a decision procedure.

For full information see cprover.org.

Versions

Get the latest release

  • Releases are tested and for production use.

Get the current develop version: git clone https://github.com/diffblue/cbmc.git

  • Develop versions are not recommended for production use.

Report bugs

If you encounter a problem please file a bug report:

Contributing to the code base

  1. Fork the repository
  2. Clone the repository git clone git@github.com:YOURNAME/cbmc.git
  3. Create a branch from the develop branch (default branch)
  4. Make your changes (follow the coding guidelines)
  5. Push your changes to your branch
  6. Create a Pull Request targeting the develop branch

New contributors can look through the mini projects page for small, focussed feature ideas.

License

4-clause BSD license, see LICENSE file.