Closed geeknik closed 3 years ago
Intriguing. I'll have to try and find a Docker image with clang 11 on it so I can take a look.
This repo might help with that. If not, this will work on a Debian or Ubuntu host:
echo "deb http://apt.llvm.org/DISTRO_NAME/ llvm-toolchain-DISTRO_NAME main" >> /etc/apt/sources.list
wget -O - https://apt.llvm.org/llvm-snapshot.gpg.key | apt-key add -
apt-get update && apt-get upgrade -y
apt-get install -y clang-11 clang-tools-11 libc++1-11 libc++-11-dev \
libc++abi1-11 libc++abi-11-dev libclang1-11 libclang-11-dev \
libclang-common-11-dev libclang-cpp11 libclang-cpp11-dev liblld-11 \
liblld-11-dev liblldb-11 liblldb-11-dev libllvm11 libomp-11-dev \
libomp5-11 lld-11 lldb-11 llvm-11 llvm-11-dev llvm-11-runtime llvm-11-tools libfuzzer-11-dev
Same thing happens with Clang 12/LLVM 12. Any thoughts?
This is no longer an issue I'm having.
If I don't touch
mainline.sh
and just run it, I get to this stage:If I update
mainline.sh
to use-fsanitize=address,fuzzer -fsanitize-coverage=trace-pc-guard
, this happens:Changing the C/CXX flags to
-fsanitize=address,fuzzer-no-link
and then passing-fsanitize=address,fuzzer
in the LD flags doesn't seem to help:clang -v
dpkg --list | grep clang
dpkg --list | grep llvm
EDIT: I removed all of the clang and llvm artifiacts that weren't from version 11. Didn't change anything.