From ae168a1398f71d18b70be42ce0562ea9dfcf1a69 Mon Sep 17 00:00:00 2001 From: Alex Groce Date: Tue, 14 May 2019 13:53:33 -0700 Subject: [PATCH] Note about using older Manticore version --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index d75f6a9..d00e719 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,9 @@ virtualenv venv python $DEEPSTATE/build/setup.py install ``` -The `virtualenv`-enabled `$PATH` should now include two executables: `deepstate` and `deepstate-angr`. These are _executors_, which are used to run DeepState test binaries with specific backends (automatically installed as Python dependencies). The `deepstate` executor uses the Manticore backend while `deepstate-angr` uses angr. They share a common interface where you may specify a number of workers and an output directory for saving backend-generated test cases. +The `virtualenv`-enabled `$PATH` should now include two executables: `deepstate` and `deepstate-angr`. These are _executors_, which are used to run DeepState test binaries with specific backends (automatically installed as Python dependencies). The `deepstate` or `deepstate-manticore` executor uses the Manticore backend while `deepstate-angr` uses angr. They share a common interface where you may specify a number of workers and an output directory for saving backend-generated test cases. + +If you try using Manticore, and it doesn't work, but you definitely have the latest Manticore installed, check the `.travis.yml` file. If that grabs a Manticore other than the master version, you can try using the version of Manticore we use in our CI tests. Sometimes Manticore makes a breaking change, and we are behind for a short time. You can check your build using the test binaries that were (by default) built and emitted to `deepstate/build/examples`. For example, to use angr to symbolically execute the `IntegerOverflow` test harness with 4 workers, saving generated test cases in a directory called `out`, you would invoke: