summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Wiederhake <BenWiederhake.GitHub@gmx.de>2021-10-21 20:20:51 +0200
committerLinus Groh <mail@linusgroh.de>2021-10-23 19:29:59 +0100
commitfc519d43baaa926aae2213d5df526abd60b493e2 (patch)
tree4d00795209290e262be0209303a9feb3ab47999b
parente503b60bdc4e08bbdafc4fc0337ea8fe2290bb69 (diff)
downloadserenity-fc519d43baaa926aae2213d5df526abd60b493e2.zip
Fuzzing: Update build instructions
The project needs clang-12, which is not on all systems the default (e.g. Debian Testing).
-rw-r--r--Meta/Lagom/ReadMe.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/Meta/Lagom/ReadMe.md b/Meta/Lagom/ReadMe.md
index 1902158740..edc80c8b50 100644
--- a/Meta/Lagom/ReadMe.md
+++ b/Meta/Lagom/ReadMe.md
@@ -29,11 +29,13 @@ Lagom can be used to fuzz parts of SerenityOS's code base. This requires buildli
# Or as a handy rebuild-rerun line:
ninja FuzzJs && ./Fuzzers/FuzzJs
+(Note that we require clang >= 12, so depending on your package manager you may need to specify `clang++-12` and `clang-12` instead.)
+
Any fuzzing results (particularly slow inputs, crashes, etc.) will be dropped in the current directory.
clang emits different warnings than gcc, so you may have to remove `-Werror` in CMakeLists.txt and Meta/Lagom/CMakeLists.txt.
-Fuzzers work better if you give them a fuzz corpus, e.g. `./Fuzzers/FuzzBMP ../Base/res/html/misc/bmpsuite_files/rgba32-61754.bmp` Pay attention that LLVM also likes creating new files, don't blindly commit them (yet)!
+Fuzzers work better if you give them a fuzz corpus, e.g. `./Fuzzers/FuzzBMPLoader ../Base/res/html/misc/bmpsuite_files/rgba32-61754.bmp` Pay attention that LLVM also likes creating new files, don't blindly commit them (yet)!
To run several fuzz jobs in parallel, pass `-jobs=24 -workers=24`.