C/C++ in devcontainer

Bug Reports
1

I’m running a devcontainer on the remote SSH machine. And C/C++ extension stopped working for me recently. I have the following messages in “C/C++” Output console:

Warning: Expected file /root/.cursor-server/extensions/anysphere.cpptools-2.0.0-linux-x64/bin/cpptools is missing.

Warning: Expected file /root/.cursor-server/extensions/anysphere.cpptools-2.0.0-linux-x64/bin/cpptools-srv is missing.

Warning: Expected file /root/.cursor-server/extensions/anysphere.cpptools-2.0.0-linux-x64/bin/cpptools-wordexp is missing.

Warning: Expected file /root/.cursor-server/extensions/anysphere.cpptools-2.0.0-linux-x64/bin/libc.so is missing.
intelliSenseEngine is disabled

I tried reinstalling Cursor and removing ~/.cursor* on the remote host. Any tips how to debug this?

3

These files are really missing:

ls /root/.cursor-server/extensions/anysphere.cpptools-2.0.0/bin
common.json             linux.clang.x64.json  linux.gcc.arm.json  macos.clang.arm64.json  macos.clang.x86.json  macos.gcc.x64.json  windows.clang.arm64.json  windows.clang.x86.json  windows.gcc.x64.json     windows.msvc.arm.json
linux.clang.arm64.json  linux.clang.x86.json  linux.gcc.x64.json  macos.clang.arm.json    macos.gcc.arm64.json  macos.gcc.x86.json  windows.clang.arm.json    windows.gcc.arm64.json  windows.gcc.x86.json     windows.msvc.x64.json
linux.clang.arm.json    linux.gcc.arm64.json  linux.gcc.x86.json  macos.clang.x64.json    macos.gcc.arm.json    messages            windows.clang.x64.json    windows.gcc.arm.json    windows.msvc.arm64.json  windows.msvc.x86.json

No libs are there.

5

Hi @dbabokin, the libc.so is not distributed with the extension. This indicates that the dynamic linker couldn’t find the library – which flavor of Linux are you on? You might need to install libc6 if it is not there.

(The other warnings about cpptools missing are expected)

Also, if you’re coming from the VSCode cpptools extension, you’ll need to configure clangd for LSP support. ClangD is bundled with our extension. This can be done by having your build utility (e.g. CMake) generate a compile_commands.json, that clangd then reads. The ClangD docs have more info for how to set this up.

6

I’m running in Ubuntu 22.04 container. I tried standard MS dev container and my own container, which is based on Ubuntu 22.04. I have clang and libc installed. What is libc version requirement in anysphere.cpptools-2.0.0 build for x64 linux?

8

I tried fresh mcr.microsoft.com/devcontainers/base:ubuntu-24.04 devcontainer - same problem. Any tips or suggestions how to debug are welcome.

10

Seeing the same thing.
Fresh container, installed anysphere c/c++ extension. Exact same error messages.

12

I also tried native remote execution. Nothing worked. I eventually switch to clangd.

14

I’m wondering, did anyone succeed to use anysphere c/c++ extension on Linux at all? What’s your setup?

16

Hi @dbabokin, could you share more about the specific issue that you’re running into? Is the LSP not responding or something else happening?

Under the scenes, our extension relies on Clangd for LSP support (we bundle it with the Anysphere C++).

17

I install “C/C++ Extension Pack”, which triggers installation of “C/C++” extension (anysphere.cpptools). My client is on macOS and I’m connecting to Linux remote (Ubuntu 22.04). I tired SSH connection and devcontainer on the remote host (Ubuntu 22.04 and Ubuntu 24.04 based). In any of these scenarios C/C++ extension fails on startup with the message in the original post and I don’t get any C/C++ browsing support.

So I have to disable “C/C++” manually and install “clangd” extension (llvm-vs-code-extensions.vscode-clangd). That is my workaround and it works fine for me. But not the “C/C++” extension.