Nathan Ridge

It looks like this crash is not specific to clangd, it also happens when trying to compile this code with `clang`. Could you report the crash upstream at https://github.com/llvm/llvm-project/issues/ please?

See https://github.com/clangd/vscode-clangd/issues/185 for a similar request.

Your logs are suggesting that clangd is still trying to find gcc 12 standard library headers. Based on previous investigations of similar issues (see [this comment](https://github.com/clangd/clangd/issues/1394#issuecomment-1328676884) in particular), the most...

Can you share verbose logs (taken with `--log=verbose` in clangd's arguments)?

Thanks, and can you say more about the "clangd extracts x86_64 includes" part? What are these x86_64 includes and where are you seeing them?

Ok, I see. And just to make sure, when you showed the output of `arm-none-eabi-gcc -x c++ -E -v -`, the full path of the compiler you were running was...

> Assuming that's the case, the only explanation I can think of is that when clangd executes that command, it has something in its environment (like `CXXFLAGS` or a similar...

> > Assuming that's the case, the only explanation I can think of is that when clangd executes that command, it has something in its environment ... > > I'm...

> I guess this implies the variables in the wrapper script are used wrong? My guess is they're right for processing code targeting the host, but the script doesn't consider...

> `clangd` should only use the default include paths if the driver is not queried, in case the driver is queried and the set of include paths are different, only...