Change --enable-fuzzing to --enable-fuzzers

Since it controls whether to build the fuzzer targets, not whether those
fuzzer targets actually use a fuzzing engine.
This commit is contained in:
Jon Siwek 2020-04-24 11:59:10 -07:00
parent 78b0b2183d
commit 6721685202
4 changed files with 8 additions and 8 deletions

View file

@ -481,7 +481,7 @@ message(
"\n debugging: ${USE_PERFTOOLS_DEBUG}" "\n debugging: ${USE_PERFTOOLS_DEBUG}"
"\njemalloc: ${ENABLE_JEMALLOC}" "\njemalloc: ${ENABLE_JEMALLOC}"
"\n" "\n"
"\nFuzz Targets: ${ZEEK_ENABLE_FUZZING}" "\nFuzz Targets: ${ZEEK_ENABLE_FUZZERS}"
"\nFuzz Engine: ${ZEEK_FUZZING_ENGINE}" "\nFuzz Engine: ${ZEEK_FUZZING_ENGINE}"
"\n" "\n"
"\n================================================================\n" "\n================================================================\n"

6
configure vendored
View file

@ -47,7 +47,7 @@ Usage: $0 [OPTION]... [VAR=VALUE]...
Optional Features: Optional Features:
--enable-debug compile in debugging mode (like --build-type=Debug) --enable-debug compile in debugging mode (like --build-type=Debug)
--enable-coverage compile with code coverage support (implies debugging mode) --enable-coverage compile with code coverage support (implies debugging mode)
--enable-fuzzing build fuzzing targets --enable-fuzzers build fuzzer targets
--enable-mobile-ipv6 analyze mobile IPv6 features defined by RFC 6275 --enable-mobile-ipv6 analyze mobile IPv6 features defined by RFC 6275
--enable-perftools enable use of Google perftools (use tcmalloc) --enable-perftools enable use of Google perftools (use tcmalloc)
--enable-perftools-debug use Google's perftools for debugging --enable-perftools-debug use Google's perftools for debugging
@ -230,8 +230,8 @@ while [ $# -ne 0 ]; do
append_cache_entry ENABLE_COVERAGE BOOL true append_cache_entry ENABLE_COVERAGE BOOL true
append_cache_entry ENABLE_DEBUG BOOL true append_cache_entry ENABLE_DEBUG BOOL true
;; ;;
--enable-fuzzing) --enable-fuzzers)
append_cache_entry ZEEK_ENABLE_FUZZING BOOL true append_cache_entry ZEEK_ENABLE_FUZZERS BOOL true
;; ;;
--enable-debug) --enable-debug)
append_cache_entry ENABLE_DEBUG BOOL true append_cache_entry ENABLE_DEBUG BOOL true

View file

@ -1,7 +1,7 @@
######################################################################## ########################################################################
## Fuzzing targets ## Fuzzing targets
if ( NOT ZEEK_ENABLE_FUZZING ) if ( NOT ZEEK_ENABLE_FUZZERS )
return() return()
endif () endif ()

View file

@ -14,7 +14,7 @@ First configure and build for fuzzing (with libFuzzer) and code coverage::
CFLAGS="-fprofile-instr-generate -fcoverage-mapping" \ CFLAGS="-fprofile-instr-generate -fcoverage-mapping" \
CXXFLAGS="-fprofile-instr-generate -fcoverage-mapping" \ CXXFLAGS="-fprofile-instr-generate -fcoverage-mapping" \
./configure --build-type=RelWithDebInfo --build-dir=./build-fuzz-cov \ ./configure --build-type=RelWithDebInfo --build-dir=./build-fuzz-cov \
--sanitizers=fuzzer-no-link --enable-fuzzing --sanitizers=fuzzer-no-link --enable-fuzzers
$ cd build-fuzz-cov && make -j $(nproc) $ cd build-fuzz-cov && make -j $(nproc)
@ -60,9 +60,9 @@ First configure and build::
$ CC=clang CXX=clang++ \ $ CC=clang CXX=clang++ \
./configure --build-type=debug --build-dir=./build-fuzz-check \ ./configure --build-type=debug --build-dir=./build-fuzz-check \
--sanitizers=address,fuzzer-no-link --enable-fuzzing --sanitizers=address --enable-fuzzers
$ cd build-fuzz-cov && make -j $(nproc) $ cd build-fuzz-check && make -j $(nproc)
Get a set of inputs to process (we're using the POP3 fuzzer/corpus as example):: Get a set of inputs to process (we're using the POP3 fuzzer/corpus as example)::