|author||Robert Loehning <firstname.lastname@example.org>||2019-06-20 12:54:49 +0200|
|committer||Robert Loehning <email@example.com>||2019-07-11 14:17:08 +0200|
Fix typos in readme
Change-Id: Ifecb1bac475512241de9bcf195955409bb3adaff Reviewed-by: Edward Welbourne <firstname.lastname@example.org> Reviewed-by: Paul Wicking <email@example.com>
1 files changed, 3 insertions, 3 deletions
diff --git a/tests/libfuzzer/README b/tests/libfuzzer/README
index 7327e76eff..57140cebfb 100644
@@ -7,7 +7,7 @@ of the test and track the code execution. Should the test crash, libFuzzer will
data which triggered the crash. You can then use this to debug and fix the called code.
! Please note: The purpose of fuzz testing is to find unexpected code paths. Running fuzz tests may!
-! result in unforeseen bevavior, including loss of data. Consider running the tests in an isolated !
+! result in unforeseen behavior, including loss of data. Consider running the tests in an isolated !
! environment, e.g. on a virtual machine. You have been warned. !
To run a test with libFuzzer:
@@ -21,7 +21,7 @@ To run a test with libFuzzer:
to add the needed code coverage instrumentation. Since speed of execution is crucial for fuzz
testing, it's recommendable to also use the switches
- It might also make sense to add sanitzers by passing
+ It might also make sense to add sanitizers by passing
4. Build Qt.
5. Build one of the tests using this Qt build.
@@ -29,7 +29,7 @@ To run a test with libFuzzer:
Depending on the expected input format of the tested function, you will get results faster if
* provide a set of interesting input data by passing the path of a directory which contains
- these data, each in one file. You can find such datasets in the subdirectory "testcases".
+ these data, each in one file. You can find such data sets in the subdirectory "testcases".
* pass a so-called dictionary listing keywords of the input format using
A couple of such dictionaries are provided by AFL (http://lcamtuf.coredump.cx/afl/)