vscode-extensions.vadimcn.vscode-lldb.adapter: intergrated terminal broken

[zspher]

For context, I'm on neovim using nvim-dap.

When debugging in a c program, I'm getting the following error and the intergrated terminal does not work. This prevents any user input (i.e. from scanf)

Console is in 'commands' mode, prefix expressions with '?'.
Failed to redirect stdio to a terminal. (Could not find codelldb-launch)
Debuggee output will appear here.

On older versions (1.11.4), the intergrated terminal appears.

[deemp]

@zspher how to reproduce?

[zspher]

to reproduce

1. run adapter with neovim

dap.adapters["codelldb"] = {
  type = "executable",
  command = "codelldb",
}


dap.configurations["c"] = {
{
  name = "Launch file",
  type = "codelldb",
  request = "launch",
  program = "${command:pickFile}",
  cwd = "${workspaceFolder}",
  args = {}
},
}

2. run a debug session on a c program
3. go to repl and see above message

do you need me to create a repro.lua for neovim (nvim -u repro.lua)?

[deemp]

@zspher please correct me if I'm wrong.

You're using not the extension but a component of the extension (the codelldb executable) in neovim.

This repo is about VS Code extensions. The components of extensions aren't guaranteed to work in other editors. Neither are extensions guaranteed to work in VS Code, btw.

So, I think your issue is out of scope for this repo.

However, you may receive help from visitors of this repo, LLMs, or you may be able to solve this problem on your own if you provide a full minimal reproducible example.

An ideal example would be a repo with all needed parts: platform specification, flake, neovim configs, etc.

[zspher]

I'll keep that in mind.
I'll probably try to work on this in a couple of weeks and see if the problem is fixed

[zspher]

Hi, I think I’ve found a fix.

It involves:

• Adding codelldb-launch as an input to adapter.nix
• Adding the following to adapter.nix under postFixup:

cp ${codelldb-launch}/bin/codelldb-launch $out/share/adapter/codelldb-launch

This works because codelldb first looks for codelldb-launch in the same directory as the codelldb binary. If it doesn’t find it there, it then searches in the main extension directory.

see relevent code: https://github.com/vadimcn/codelldb/blob/39d9accd8c666e3d3d1372abccad12b3d256ed0b/src/codelldb/src/terminal.rs#L32-L48

In our case, the .adapter output does not contain either the full extension directory or the codelldb-launch binary, so the lookup fails. Copying codelldb-launch into $out/share/adapter ensures it’s available in the expected location.