make changes requested, fix cut/paste error, etc.
This commit is contained in:
parent
12ff87a15b
commit
ffdd449f07
21
README.md
21
README.md
@ -46,7 +46,7 @@ Runtime:
|
|||||||
|
|
||||||
## Building on Ubuntu 16.04 (Xenial)
|
## Building on Ubuntu 16.04 (Xenial)
|
||||||
|
|
||||||
AFL```shell
|
```shell
|
||||||
sudo apt update && sudo apt-get install build-essential gcc-multilib g++-multilib cmake python python-setuptools libffi-dev z3
|
sudo apt update && sudo apt-get install build-essential gcc-multilib g++-multilib cmake python python-setuptools libffi-dev z3
|
||||||
git clone https://github.com/trailofbits/deepstate deepstate
|
git clone https://github.com/trailofbits/deepstate deepstate
|
||||||
mkdir deepstate/build && cd deepstate/build
|
mkdir deepstate/build && cd deepstate/build
|
||||||
@ -91,15 +91,16 @@ DeepState consists of a static library, used to write test harnesses, and comman
|
|||||||
|
|
||||||
## Fuzzing with libFuzzer
|
## Fuzzing with libFuzzer
|
||||||
|
|
||||||
If you install a recent-enough clang, and run `cmake` when you install
|
If you install clang 6.0 or later, and run `cmake` when you install
|
||||||
with `BUILD_LIBFUZZER` defined, you can generate tests using LlibFuzzer.
|
with the `BUILD_LIBFUZZER` environment variable defined, you can
|
||||||
Because both DeepState and libFuzzer want to be `main`, this requires
|
generate tests using LlibFuzzer. Because both DeepState and libFuzzer
|
||||||
building a different executable for libFuzzer. The `examples`
|
want to be `main`, this requires building a different executable for
|
||||||
directory shows how this can be done. The libFuzzer executable works
|
libFuzzer. The `examples` directory shows how this can be done. The
|
||||||
like any other libFuzzer executable, and the tests produced can be run
|
libFuzzer executable works like any other libFuzzer executable, and
|
||||||
using the normal DeepState executable. For example, generating some
|
the tests produced can be run using the normal DeepState executable.
|
||||||
tests of the `OneOf` example (up to 5,000 runs), then running those
|
For example, generating some tests of the `OneOf` example (up to 5,000
|
||||||
tests to examine the results, would look like:
|
runs), then running those tests to examine the results, would look
|
||||||
|
like:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
mkdir OneOf_corpus
|
mkdir OneOf_corpus
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user