Breakpoints are getting rejected when starting debugging with netcoredbg

[acikgozb]

Hello, I'm trying to setup a basic debugging experience for C# by using nvim-dap and netcoredbg.

I installed netcoredbg via Mason, and added it to my dap config like this:

		local home_path = os.getenv("HOME")
		dap.adapters.coreclr = {
			type = "executable",
			command = home_path .. "/.local/share/nvim/mason/bin/netcoredbg",
			args = { "--interpreter=vscode" },
		}

		dap.configurations.cs = {
			{
				type = "coreclr",
				name = "launch - netcoredbg",
				request = "launch",
				program = function()
					if vim.fn.confirm("Should I recompile first?", "&yes\n&no", 2) == 1 then
						vim.g.dotnet_build_project()
					end
					return vim.g.dotnet_get_dll_path()
				end,
			},
		}

The functions dotnet_build_project and dotnet_get_dll_path are taken from the cookbook.

When I toggle a breakpoint and then start debugging via continue(), I see breakpoint letters changing to R from B.

I checked the logs from dap and saw that my breakpoints are not verified:

[ DEBUG ] 2024-02-12T09:52:17Z+0300 ] ...gozb/.local/share/nvim/lazy/nvim-dap/lua/dap/session.lua:1676 ]	"request"	{
  arguments = {
    name = "launch - netcoredbg",
    program = "/Users/acikgozb/personal-projects/net-web-api-playground/NetWebApi/bin/Debug/net8.0/NetWebApi.dll",
    request = "launch",
    type = "coreclr"
  },
  command = "launch",
  seq = 3,
  type = "request"
}
[ DEBUG ] 2024-02-12T09:52:17Z+0300 ] ...gozb/.local/share/nvim/lazy/nvim-dap/lua/dap/session.lua:950 ]	1	{
  body = {
    breakpoints = { {
        id = 1,
        line = 18,
        message = "The breakpoint is pending and will be resolved when debugging starts.",
        verified = false
      } }
  },
  command = "setBreakpoints",
  request_seq = 2,
  seq = "4",
  success = true,
  type = "response"
}
[ INFO ] 2024-02-12T09:52:17Z+0300 ] ...gozb/.local/share/nvim/lazy/nvim-dap/lua/dap/session.lua:888 ]	"Breakpoint unverified"	{
  id = 1,
  line = 18,
  message = "The breakpoint is pending and will be resolved when debugging starts.",
  verified = false
}

Probably I'm missing something really simple in my configuration but I couldn't find out. Any help would be really appreciated.

[Rimann91]

DId you ever figure this out? Im having the exact same issue

[hockic]

@Rimann91

try this if you are on windows

vim.opt.shellslash = false
vim.defer_fn(function()
  vim.opt.shellslash = false
end, 5000)

setting shellslash to false ensures that neovim uses the platform specific path separator i.e. backslash on windows -> which netcoredbg expects when working with paths
setting shellslash to true converts backslashes to forward slashes which will cause breakpoints to be rejected on some setups

some related issues

• Netcoredbg not stopping on breakpoints #1337
• "Unverified Breakpoint" Samsung/netcoredbg#40

[immanonner]

Thank you for helping me with a somewhat related problem using nvim-jdtls and its debug adapters! I threw that setting at the top of my ftplugin\java.lua file and my breakpoints were finally recognized (not auto rejected) by nvim-dap.