aboutsummaryrefslogtreecommitdiff
path: root/ci/test/00_setup_env_native_fuzz.sh
diff options
context:
space:
mode:
authorfanquake <fanquake@gmail.com>2023-11-07 14:05:25 +0000
committerfanquake <fanquake@gmail.com>2023-11-07 16:57:23 +0000
commit49d953281df5618430728c0a88471695207f086b (patch)
treef68b9a6fdd6b894b8941d028b59d069aab1539b3 /ci/test/00_setup_env_native_fuzz.sh
parent3da69c464f16841a5c8d9fcc9c63238ab807d5ff (diff)
downloadbitcoin-49d953281df5618430728c0a88471695207f086b.tar.xz
fuzz: explicitly specify llvm-symbolizer path in runner
It's not completely clear to me why this needs to be explicitly specified in some environments, and not in others, while at the same time that `llvm-symbolizer` is already in PATH, but this has fixed the 2 issues outlined in #28147. Use `LLVM_SYMBOLIZER_PATH` as the env var, as that is somewhat also used inside LLVM, but not consistently, i.e it's checked for in the asan_symbolize script, but not in in the ubsan_symbolize script, or from in compiler-rt.
Diffstat (limited to 'ci/test/00_setup_env_native_fuzz.sh')
-rwxr-xr-xci/test/00_setup_env_native_fuzz.sh1
1 files changed, 1 insertions, 0 deletions
diff --git a/ci/test/00_setup_env_native_fuzz.sh b/ci/test/00_setup_env_native_fuzz.sh
index 122f044b58..3585b2b417 100755
--- a/ci/test/00_setup_env_native_fuzz.sh
+++ b/ci/test/00_setup_env_native_fuzz.sh
@@ -18,3 +18,4 @@ export CI_CONTAINER_CAP="--cap-add SYS_PTRACE" # If run with (ASan + LSan), the
export BITCOIN_CONFIG="--enable-fuzz --with-sanitizers=fuzzer,address,undefined,float-divide-by-zero,integer \
CC='clang-17 -ftrivial-auto-var-init=pattern' CXX='clang++-17 -ftrivial-auto-var-init=pattern'"
export CCACHE_MAXSIZE=200M
+export LLVM_SYMBOLIZER_PATH="/usr/bin/llvm-symbolizer-17"