MIDebuggerPath Problems by using vscode-tools in Neovim

[TerryBLK]

Hello, every developers. Now I'm looking for help. I’m new Neovim coder on C++ and Python.
For now, My Question is as follows:

I'm following README to setup nvim-dap , and Python is going well.
But for C++, it come out this problem.

How can I do to solve this problem ?

My nvim-dap setting :

local dap_status, dap = pcall(require,"dap")

if not dap_status then
  return
end

dap.set_log_level "TRACE"
vim.g.dap_virtual_text=true

vim.fn.sign_define('DapBreakpoint', {text='🛑', texthl='', linehl='', numhl=''})

--Python Settings
dap.adapters.python = {
  type = 'executable';
  command = os.getenv('HOME') .. '/.virtualenvs/debugpy/bin/python';
  args = { '-m', 'debugpy.adapter' };
}
dap.configurations.python = {
  {
    type = 'python';
    request = 'launch';
    name = "Launch file";
    program = "${file}";
    pythonPath = function()
      -- debugpy supports launching an application with a different interpreter then the one used to launch debugpy itself.
      -- The code below looks for a `venv` or `.venv` folder in the current directly and uses the python within.
      -- You could adapt this - to for example use the `VIRTUAL_ENV` environment variable.
      local cwd = vim.fn.getcwd()
      -- local venv = os.getenv("VIRTUAL_ENV")
      if vim.fn.executable(cwd .. '/venv/bin/python3') == 1 then
        return cwd .. '/venv/bin/python3'
      elseif vim.fn.executable(cwd .. '/.venv/bin/python3') == 1 then
        return cwd .. '/.venv/bin/python3'
      else
        return '/Library/Frameworks/Python.framework/Versions/3.10/bin/python3'
      end
    end;
  },
}

-- Cpp Settings
dap.adapters.cppdbg = {
  id = 'cppdbg',
  type = 'executable',
  command = os.getenv('HOME')..'/.config/nvim/lua/user/dap/debugger/cpptools-osx/extension/debugAdapters/bin/OpenDebugAD7',
}
dap.configurations.cpp = {
  {
    name = "Launch file",
    type = "cppdbg",
    request = "launch",
    program = function()
      return vim.fn.input('Path to executable: ', vim.fn.getcwd() .. '/', 'file')
    end,
    cwd = '${workspaceFolder}',
    stopOnEntry = true,
    setupCommands = {
          {
                  text = "-enable-pretty-printing",
                  description = "enable pretty printing",
                  ignoreFailures = false,
          },
    },
  },
  {
    name = 'Attach to gdbserver :1234',
    type = 'cppdbg',
    request = 'launch',
    MIMode = 'gdb',
    miDebuggerServerAddress = 'localhost:1234',
    miDebuggerPath = '/usr/bin/gdb',
    cwd = '${workspaceFolder}',
    program = function()
      return vim.fn.input('Path to executable: ', vim.fn.getcwd() .. '/', 'file')
    end,
  },
}

[theHamsta]

Could this be a capitalization issue. Did you try to specify MIDebuggerPath the way it spells it?

[TerryBLK]

Thanks for your suggestion.
I add MIDebugerPath to dap.configurations.cpp.
Well, it seems work , but the another problem come out.

Repl shows as follow, I don't know how the argument interpreter=mi came out. I don't set anything of it.

Starting: "/Users/shz/.config/nvim/lua/user/dap/debugger/cpptools-osx/extension/debugAdapters/bin/OpenDebugAD7" --interpreter=mi
OpenDebugAD7: ERROR: Unknown command line argument '--interpreter=mi'.
"/Users/shz/.config/nvim/lua/user/dap/debugger/cpptools-osx/extension/debugAdapters/bin/OpenDebugAD7" exited with code 255 (0xFF).

New setting:

-- Cpp Settings
dap.adapters.cppdbg = {
  id = 'cppdbg',
  type = 'executable',
  command = os.getenv('HOME')..'/.config/nvim/lua/user/dap/debugger/cpptools-osx/extension/debugAdapters/bin/OpenDebugAD7',
}
dap.configurations.cpp = {
  {
    name = "Launch file",
    type = "cppdbg",
    request = "launch",
    miDebuggerPath = os.getenv('HOME')..'/.config/nvim/lua/user/dap/debugger/cpptools-osx/extension/debugAdapters/bin/OpenDebugAD7',
    program = function()
      return vim.fn.input('Path to executable: ', vim.fn.getcwd() .. '/', 'file')
    end,
    cwd = '${workspaceFolder}',
    stopOnEntry = true,
    setupCommands = {
          {
                  text = "-enable-pretty-printing",
                  description = "enable pretty printing",
                  ignoreFailures = false,
          },
    },
  },
  {
    name = 'Attach to gdbserver :1234',
    type = 'cppdbg',
    request = 'launch',
    MIMode = 'gdb',
    miDebuggerServerAddress = 'localhost:1234',
    miDebuggerPath = '/usr/bin/gdb',
    cwd = '${workspaceFolder}',
    program = function()
      return vim.fn.input('Path to executable: ', vim.fn.getcwd() .. '/', 'file')
    end,
  },
}

[TerryBLK]

I find these content in vscode-cpptools.
I will try it,and see how it goes.

The path to the debugger (such as gdb). When only the executable is specified, it will search the operating system's PATH variable for a debugger (GDB on Linux and Windows, LLDB on OS X).

[nyngwang]

@TerryBLK What's the result? Thanks!

[ochsavidare]

I think you should give it with a capital letter, i.e. miDebuggerPath -> MIDebuggerPath.

And also in your new settings for the ‘launch’ option you’re pointing towards OpenDebugAD7 and not gdb.