Nathan Ridge

This is a known limitation of the design of clangd's index. See https://github.com/clangd/clangd/issues/1101 and https://github.com/clangd/clangd/issues/1673 (and particularly the first paragraph of [this comment](https://github.com/clangd/clangd/issues/1673#issuecomment-1594124865)) for additional discussion.

You could use https://clangd.llvm.org/config.html#suppress. However please be aware the clangd's functionality is going to be impaired if it's not able to correctly parse code in included header files.

Could you share a log taken with `--log=verbose` present in vscode's `"clangd.arguments"` setting?

I haven't looked in detail (e.g. to determine whether this is a duplicate), but in case it helps, here are some existing issues on file about setups involving symlinks: https://github.com/clangd/clangd/issues/413...

In your third screenshot, you have the setting name misspelled as `"clang.path"` rather than `"clangd.path"`.

It's hard to reason about the appropriateness of the "possible fix" without having some more context. Do you know **what** buffer is not terminated here? Can you provide the rest...

@syrajendra would you mind re-filing this issue at https://github.com/llvm/llvm-project/issues/ please? (I can't transfer it myself because the repo is in a different Github org.) There we can ask folks more...

Are you able to reproduce similar behaviour in a minimal project?

> Clang only added support for different documentation formats in version 22, see https://clangd.llvm.org/config#commentformat That has to do with how the contents of the comment are interpreted/parsed, and how the...

@SoCuul My objective-c knowledge is limited, but it seems to work for me on a trivial example: ```objc @interface Waldo /* Documentation for location property */ @property(readonly, assign) int location;...