From 758bc770a8f2a35e1ec142f9564f2aeac3ce33bc Mon Sep 17 00:00:00 2001 From: hexcoder <hexcoder-@users.noreply.github.com> Date: Fri, 30 Apr 2021 12:02:26 +0200 Subject: [PATCH] typos --- frida_mode/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/frida_mode/README.md b/frida_mode/README.md index 0d655d0f8..ddba6928c 100644 --- a/frida_mode/README.md +++ b/frida_mode/README.md @@ -68,7 +68,7 @@ following options are currently supported. Additionally, the intention is to be able to make a direct performance comparison between the two approaches. Accordingly, FRIDA mode includes various -tests target based on the [libpng](https://libpng.sourceforge.io/) benchmark used by +test targets based on the [libpng](https://libpng.sourceforge.io/) benchmark used by [fuzzbench](https://google.github.io/fuzzbench/) and integrated with the [StandaloneFuzzTargetMain](https://raw.githubusercontent.com/llvm/llvm-project/main/compiler-rt/lib/fuzzer/standalone/StandaloneFuzzTargetMain.c) from the llvm project. These tests include basic fork-server support, persistent mode @@ -112,9 +112,9 @@ to push and pop the full register context. Note that since this instrumentation is used on every basic block to generate coverage, it has a large impact on performance. -CompLog support also adds code to the assembly, however, at present this code +CmpLog support also adds code to the assembly, however, at present this code makes use of a basic C function and is yet to be optimized. Since not all -instances run CompLog mode and instrumentation of the binary is less frequent +instances run CmpLog mode and instrumentation of the binary is less frequent (only on CMP, SUB and CALL instructions) performance is not quite so critical. # Advanced configuration options -- GitLab