Nathan Ridge
Nathan Ridge
I think part of the reason for the lack of progress here is that this is a hard technical problem. The efforts which I think have the potential to significantly...
> Still not fixed in 2025... Please see what I wrote [here](https://github.com/clangd/clangd/issues/123#issuecomment-3255307617).
Can you share [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs)?
Some existing discussion of implementation challenges around loading plugins can be found at https://reviews.llvm.org/D92155
> These projects go to great lengths implementing their own plugin(s), adding a version-locked clangd to the toolchain is a relatively small extra step that won't be a problem. Couldn't...
I think that, as with #45, the project would be open to contributions towards plugin support that thoughtfully address the issues raised in the previous technical discussion (mostly in https://reviews.llvm.org/D92155)....
> So, as an author of clang-tidy out-of-tree check-plugin I need to know which clang-tidy version clangd is linked against, get access to the same version and link my plugin...
What impact would this have on what a stack trace printed during a crash looks like?
The release packages are intended for users, but we get crash reports from users fairly regularly, and having symbolized stack traces is pretty important for making the crash reports actionable....
Added myself as a reviewer because I'd like to review this as well before it is merged.