Segmentation fault (core dumped) with steps to reproduce

[mpownby]

Randomly, I am seeing error messages like this:

PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace, preprocessed source, and associated run script.
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var LLVM_SYMBOLIZER_PATH to point to it):
[###############-----------------] 152/318Segmentation fault (core dumped)

It seems to happen more if I mutate google test and my google test runner (which I was doing by accident). I figure even though this is not a best practice, it still feels like a defect for it to segfault (I'd expect it to just execute slower) so I'm reporting it.

---

Steps to duplicate:

From a native ubuntu 24.04 bash prompt, run this docker command:

docker run --rm -ti ubuntu:24.04 sh -c "\
	apt update -y && DEBIAN_FRONTEND=noninteractive TZ=Etc/UTC apt install -y git curl net-tools cmake clang-17 && \
	curl -1sLf 'https://dl.cloudsmith.io/public/mull-project/mull-stable/setup.deb.sh' | bash && \
	apt update -y && apt install -y mull-17 && \
	git clone --depth 1 https://github.com/RulecityLLC/LaserdiscPlayerAbstract.git &&
	cd LaserdiscPlayerAbstract && mkdir build && cd build && \
	CC=clang-17 CXX=clang++-17 cmake .. -DCMAKE_C_FLAGS=\"-O0 -fpass-plugin=/usr/lib/mull-ir-frontend-17 -g -grecord-command-line\" -DCMAKE_CXX_FLAGS=\"-O0 -fpass-plugin=/usr/lib/mull-ir-frontend-17 -g -grecord-command-line\" -DBUILD_TESTING=ON && \
	/bin/bash"

Once the above command finishes, you'll be inside a bash shell in a docker container. Just run "make -j 16" and "make clean" until you see the error. It happened to me twice the second time I did a build.