Nathan Ridge

Unfortunately the second stack trace is still not symbolized. This is the stack trace from your second log: ``` PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash...

The first part is on file as https://github.com/clangd/clangd/issues/965. We can use this ticket to track the second part (snippet with all initializers).

> > We can use this ticket to track the second part (snippet with all initializers). > > Does this feature go into clangd or the extension? I think it...

I tried bumping the image version to macos-14, but the build now [fails](https://github.com/HighCommander4/clangd/actions/runs/20048306006/job/57498702178) at the "Build gRPC" step with: ``` [1232/1864] Building CXX object third_party/abseil-cpp/absl/random/CMakeFiles/absl_random_internal_randen_hwaes_impl.dir/internal/randen_hwaes.cc.o FAILED: [code=1] third_party/abseil-cpp/absl/random/CMakeFiles/absl_random_internal_randen_hwaes_impl.dir/internal/randen_hwaes.cc.o /usr/bin/clang++ -I/Users/runner/work/clangd/clangd/grpc/third_party/abseil-cpp...

> > Build success, but failed at check binary compatibility > > ``` > > Run .github/workflows/lib_compat_test.py --lib=GLIBC_2.18 "$CLANGD_DIR/bin/clangd" > > Binary depends on disallowed symbols above. Use some combination...

We have a list of mappings from internal headers to standard headers [here](https://searchfox.org/llvm/rev/16aa79d444a32c8d8b4f2e60d58f785e47178987/clang-tools-extra/clangd/index/CanonicalIncludes.cpp#652), maybe `_ssize_t.h` needs to be added there.

I'm not quite sure what "switch clangd to 32-bit mode" means. Can you share some more details, e.g. what is the manual configuration that you're applying today that you'd like...

> Simply `-m32` clang flag. I want a similar option for clangd because I develop only for x86-32 and don't want to create compile_flags.txt and alternatives each time. This sounds...

I don't think we're likely to add a new command-line option specifically for adding `-m32` to compile commands. However, the possibility of specifying arbitrary configuration file options on the command...

> However, the possibility of specifying arbitrary configuration file options on the command line has come up before, specifically [here](https://github.com/clangd/clangd/discussions/1782#discussioncomment-7249799): > > > 2. Add a command-line flag `--config-fragment=`, which...