Fix typos - 1st run

This commit is contained in:
llzmb 2021-12-02 21:23:22 +01:00
parent 377adb776e
commit aa6586a761
6 changed files with 8 additions and 8 deletions

View File

@ -1,6 +1,6 @@
# GramaTron
Gramatron is a coverage-guided fuzzer that uses grammar automatons to perform
GramaTron is a coverage-guided fuzzer that uses grammar automatons to perform
grammar-aware fuzzing. Technical details about our framework are available
in the [ISSTA'21 paper](https://nebelwelt.net/files/21ISSTA.pdf).
The artifact to reproduce the experiments presented in the paper are present
@ -9,11 +9,11 @@ grammars is presented below:
# Compiling
Execute `./build_gramatron_mutator.sh`
Execute `./build_gramatron_mutator.sh`.
# Running
You have to set the grammar file to use with `GRAMMATRON_AUTOMATION`:
You have to set the grammar file to use with `GRAMATRON_AUTOMATION`:
```
export AFL_DISABLE_TRIM=1

View File

@ -125,7 +125,7 @@ If you find an interesting or important question missing, submit it via
If, however, randomness happens, e.g., a thread reading other external data,
reaction to timing, etc., then in some of the re-executions with the same data
the edge coverage result will be different accross runs. Those edges that
the edge coverage result will be different across runs. Those edges that
change are then flagged "unstable".
The more "unstable" edges, the more difficult for AFL++ to identify valid new paths.

View File

@ -131,7 +131,7 @@ The following options are available when you instrument with LTO mode
have to compile the target twice, once specifically with/for this mode by
setting `AFL_LLVM_CMPLOG=1`, and pass this binary to afl-fuzz via the `-c`
parameter. Note that you can compile also just a cmplog binary and use that
for both, however, there will be a performance penality. You can read more
for both, however, there will be a performance penalty. You can read more
about this in
[instrumentation/README.cmplog.md](../instrumentation/README.cmplog.md).

View File

@ -125,7 +125,7 @@ For splitting memcmp, strncmp, etc., see
Then there are different ways of instrumenting the target:
1. An better instrumentation strategy uses LTO and link time instrumentation.
1. A better instrumentation strategy uses LTO and link time instrumentation.
Note that not all targets can compile in this mode, however, if it works it
is the best option you can use. To go with this option, use
afl-clang-lto/afl-clang-lto++. See [README.lto.md](README.lto.md).

View File

@ -31,7 +31,7 @@ The AFL_COMPCOV_LEVEL tells to QEMU and libcompcov how to log comaprisons.
Level 1 logs just comparison with immediates / read-only memory and level 2
logs all the comparisons.
The library make use of https://github.com/ouadev/proc_maps_parser and so it is
The library makes use of https://github.com/ouadev/proc_maps_parser and so it is
Linux specific. However, this is not a strict dependency, other UNIX operating
systems can be supported by replacing the code related to the /proc/self/maps
parsing.

View File

@ -77,7 +77,7 @@ For more details, see the paper
[Seed Selection for Successful Fuzzing](https://dl.acm.org/doi/10.1145/3460319.3464795).
If you use OptiMin in your research, please cite this paper.
Bibtex:
BibTeX:
```bibtex
@inproceedings{Herrera:2021:FuzzSeedSelection,