Nathan Ridge

> The behavior of clangd not working in a specific project is that code navigation, all code suggestions, and code parsing fail to function properly, while clang-tidy still seems to...

What I'm seeing in this log is that you are performing go-to-definition on a line that looks like this: ```c++ #define MAX_MINOR (10) ``` with the cursor over the `MAX_MINOR`...

> For example, at this moment, when I try to jump to the definition of a function called my_open, it remains frozen. Which file and line are you jumping from?

> I followed your instructions and opened the current file main_bus.c, specifically the my_open function in the main_bus.c file. I do see in the log that go-to-definition is invoked on...

Is the file you're editing a header? It's expected that clangd re-parses open tabs which include the header when a header changes (since changing the header may e.g. introduce new...

Is this on valid or invalid code? There are some existing clang bugs of a crash on invalid code with a similar backtrace: https://github.com/llvm/llvm-project/issues/63250, https://github.com/llvm/llvm-project/issues/107835, this might be a duplicate....

> However, when I checked the clangd's log, `/usr/lib/gcc/x86_64-linux-gnu/6/include` is missing. > > ``` > I[16:52:40.824] System includes extractor: successfully executed /usr/bin/g++ > got includes: "/usr/include/c++/6, /usr/include/x86_64-linux-gnu/c++/6, /usr/include/c++/6/backward, /usr/local/include, /usr/lib/gcc/x86_64-linux-gnu/6/include-fixed,...

> For some reason, the "--compile-commands-dir" parameter now makes the "--query-driver" parameter invalid. You can't use these two parameters at the same time Using those two parameters together should work...

@USTHzhanglu feel free to share clangd logs for further diagnosis (preferably in a new issue).

> I am wondering how the release process work. When do you plan to publish the next one on the marketplace? vscode-clangd does not currently have a regular release schedule....