ExternalVendorCode/AFLplusplus
1
0
Fork 0
mirror of https://github.com/AFLplusplus/AFLplusplus.git synced 2025-06-10 17:21:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

Change "eg" to "e.g." and fix punctuation

Browse Source
This commit is contained in:
llzmb 2021-12-02 21:16:16 +01:00
parent 65c3db8625
commit 377adb776e
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
custom_mutators/gramatron/README.md
View File

@ -28,18 +28,20 @@ afl-fuzz -i in -o out -- ./target
- Specify in a JSON format for CFG. Examples are correspond `source.json` files - Specify in a JSON format for CFG. Examples are correspond `source.json` files
- Run the automaton generation script (in `src/gramfuzz-mutator/preprocess`) - Run the automaton generation script (in `src/gramfuzz-mutator/preprocess`)
which will place the generated automaton in the same folder. which will place the generated automaton in the same folder.
``` ```
./preprocess/prep_automaton.sh <grammar_file> <start_symbol> [stack_limit] ./preprocess/prep_automaton.sh <grammar_file> <start_symbol> [stack_limit]
Eg. ./preprocess/prep_automaton.sh ~/grammars/ruby/source.json PROGRAM E.g., ./preprocess/prep_automaton.sh ~/grammars/ruby/source.json PROGRAM
``` ```
- If the grammar has no self-embedding rules then you do not need to pass the - If the grammar has no self-embedding rules then you do not need to pass the
stack limit parameter. However, if it does have self-embedding rules then you stack limit parameter. However, if it does have self-embedding rules then you
need to pass the stack limit parameter. We recommend starting with `5` and need to pass the stack limit parameter. We recommend starting with `5` and
then increasing it if you need more complexity then increasing it if you need more complexity
- To sanity-check that the automaton is generating inputs as expected you can use the `test` binary housed in `src/gramfuzz-mutator` - To sanity-check that the automaton is generating inputs as expected you can use the `test` binary housed in `src/gramfuzz-mutator`
``` ```
./test SanityCheck <automaton_file> ./test SanityCheck <automaton_file>
Eg. ./test SanityCheck ~/grammars/ruby/source_automata.json E.g., ./test SanityCheck ~/grammars/ruby/source_automata.json
``` ```

2
docs/fuzzing_in_depth.md
View File

@ -175,7 +175,7 @@ The following sanitizers have built-in support in AFL++:
* ASAN = Address SANitizer, finds memory corruption vulnerabilities like * ASAN = Address SANitizer, finds memory corruption vulnerabilities like
use-after-free, NULL pointer dereference, buffer overruns, etc. Enabled with use-after-free, NULL pointer dereference, buffer overruns, etc. Enabled with
`export AFL_USE_ASAN=1` before compiling. `export AFL_USE_ASAN=1` before compiling.
* MSAN = Memory SANitizer, finds read access to uninitialized memory, eg. a * MSAN = Memory SANitizer, finds read access to uninitialized memory, e.g., a
local variable that is defined and read before it is even set. Enabled with local variable that is defined and read before it is even set. Enabled with
`export AFL_USE_MSAN=1` before compiling. `export AFL_USE_MSAN=1` before compiling.
* UBSAN = Undefined Behavior SANitizer, finds instances where - by the C and C++ * UBSAN = Undefined Behavior SANitizer, finds instances where - by the C and C++