duckdb: Compile in relassert mode and enable CRASH_ON_ASSERT for fuzzing (#9904)

This should enable assertion checking, and sets it up so DuckDB calls
`abort()` on any assertion trigger, which should lead to more effective
fuzzing.
This commit is contained in:
Mark 2023-03-11 18:16:16 +01:00 committed by GitHub
parent 0b607feb21
commit 7f992d802f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions

View File

@ -15,10 +15,10 @@
#
################################################################################
make
EXTENSION_LIBS=$(find ./build/release/extension/ -name "*.a")
THIRD_PARTY_LIBS=$(find ./build/release/third_party/ -name "*.a")
make relassert CRASH_ON_ASSERT=1 DISABLE_SANITIZER=1
EXTENSION_LIBS=$(find ./build/relassert/extension/ -name "*.a")
THIRD_PARTY_LIBS=$(find ./build/relassert/third_party/ -name "*.a")
$CXX $CXXFLAGS $LIB_FUZZING_ENGINE ./test/ossfuzz/parse_fuzz_test.cpp \
-o $OUT/parse_fuzz_test -I./ -I./src/include \
./build/release/src/libduckdb_static.a \
./build/relassert/src/libduckdb_static.a \
${EXTENSION_LIBS} ${THIRD_PARTY_LIBS}