diff options
| author | hexcoder <hexcoder-@users.noreply.github.com> | 2021-03-05 18:11:05 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-05 18:11:05 +0100 |
| commit | 16d6f35aa6f968d6dbdd2005e8fa140955815837 (patch) | |
| tree | 4b8ff6116773e8d1d90c0f993a8ac6a63988dc93 | |
| parent | c9854ec8cbd87dc09d7a6ab1b75f3fce2f7bc9ca (diff) | |
| download | afl++-16d6f35aa6f968d6dbdd2005e8fa140955815837.tar.gz | |
typos
| -rw-r--r-- | instrumentation/README.ctx.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/instrumentation/README.ctx.md b/instrumentation/README.ctx.md index ffcce0a9..577b3e5f 100644 --- a/instrumentation/README.ctx.md +++ b/instrumentation/README.ctx.md @@ -4,7 +4,7 @@ This is an LLVM-based implementation of the context sensitive branch coverage. -Basically every function gets its own ID and, every time that an edge is logged, +Basically every function gets its own ID and, every time when an edge is logged, all the IDs in the callstack are hashed and combined with the edge transition hash to augment the classic edge coverage with the information about the calling context. @@ -16,7 +16,7 @@ In math the coverage is collected as follows: `map[current_location_ID ^ previous_location_ID >> 1 ^ hash_callstack_IDs] += 1` The callstack hash is produced XOR-ing the function IDs to avoid explosion with -recusrsive functions. +recursive functions. ## Usage @@ -28,7 +28,7 @@ many map collisions occur. ## Caller Branch Coverage -If the context sensitive coverage introduces too may collisions becoming +If the context sensitive coverage introduces too may collisions and becoming decremental, the user can choose to augment edge coverage with just the called function ID, instead of the entire callstack hash. |