mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
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:
parent
78b0b2183d
commit
6721685202
4 changed files with 8 additions and 8 deletions
|
@ -481,7 +481,7 @@ message(
|
|||
"\n debugging: ${USE_PERFTOOLS_DEBUG}"
|
||||
"\njemalloc: ${ENABLE_JEMALLOC}"
|
||||
"\n"
|
||||
"\nFuzz Targets: ${ZEEK_ENABLE_FUZZING}"
|
||||
"\nFuzz Targets: ${ZEEK_ENABLE_FUZZERS}"
|
||||
"\nFuzz Engine: ${ZEEK_FUZZING_ENGINE}"
|
||||
"\n"
|
||||
"\n================================================================\n"
|
||||
|
|
6
configure
vendored
6
configure
vendored
|
@ -47,7 +47,7 @@ Usage: $0 [OPTION]... [VAR=VALUE]...
|
|||
Optional Features:
|
||||
--enable-debug compile in debugging mode (like --build-type=Debug)
|
||||
--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-perftools enable use of Google perftools (use tcmalloc)
|
||||
--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_DEBUG BOOL true
|
||||
;;
|
||||
--enable-fuzzing)
|
||||
append_cache_entry ZEEK_ENABLE_FUZZING BOOL true
|
||||
--enable-fuzzers)
|
||||
append_cache_entry ZEEK_ENABLE_FUZZERS BOOL true
|
||||
;;
|
||||
--enable-debug)
|
||||
append_cache_entry ENABLE_DEBUG BOOL true
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
########################################################################
|
||||
## Fuzzing targets
|
||||
|
||||
if ( NOT ZEEK_ENABLE_FUZZING )
|
||||
if ( NOT ZEEK_ENABLE_FUZZERS )
|
||||
return()
|
||||
endif ()
|
||||
|
||||
|
|
|
@ -14,7 +14,7 @@ First configure and build for fuzzing (with libFuzzer) and code coverage::
|
|||
CFLAGS="-fprofile-instr-generate -fcoverage-mapping" \
|
||||
CXXFLAGS="-fprofile-instr-generate -fcoverage-mapping" \
|
||||
./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)
|
||||
|
||||
|
@ -60,9 +60,9 @@ First configure and build::
|
|||
|
||||
$ CC=clang CXX=clang++ \
|
||||
./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)::
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue