You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: