Just to confirm, do you see these errors in your editor? If not, there may be an issue with your editor configuration where it's not showing diagnostics from clangd. If you do see them, well, they're the reason why go-to-definition is not working :) The last ...
Lately I’m working on a refactor in the append pipeline of the MediaSource Extensions implementation of the WebKit for the GStreamer ports. Working on refactors often triggers many build issues, not only because they often encompass a lot of code, but also because it’s very easy to ...
[clangd] Fix Go to Definition not working in VSCode extension[clangd] Extract FsPath from file:// uri[clangd] Add support for vscode extension configuration[clangd] Add support for FixIts.[clangd] Add a toy VS Code integration for development purposes...
However, we want locateMacroAt() to find the macro definition in both of these cases. We have an existing workaround for #undef: we adjust the token location, moving it forward by one token. The modified location now passes the "the #undef comes after" check. We do not have a ...
clangd gives the error error: In included file: definition of builtin function '__rdtsc' when including the SDL.h header file from SDL2, using clangd lsp in neovim on Windows, with the MSYS2 mingw64 gcc compiler passed as an argument to ...
includingGo to declaration/definition, highlighting references under the caret, the Quick Documentation Popup, andFind usages. The results we get from Clangd-based engine are still reviewed and adjusted by CLion, so the two engines still work in parallel to give you the most accurate and reasonabl...
haven been disabled for now and do not working in clangd-vscode-multi-project. Releases 0.1.0 - 29/02/2024 (based on vscode-clangd@0.1.26) Setup clangd server The extension requires the clangd language server. You will be prompted to download it if it's not found on your PATH. (...
That said, I'm not 100% confident either without trying it, and particularly may be overlooking Windows-specific considerations. If it's not working for you, please feel free to post clangd logs (preferably in a new issue) and we can help figure out what's going wrong. ...
I would characterize this as a bug in glibc malloc which we're working around, clangd on FreeBSD should not be affected. Clangd uses a fair amount of memory in any case, but that's not really what this bug is about - here we had a 10x overhead of memory free()d by clangd but ...