Closed ibhagwan closed 3 months ago
FYI, did some more testing on this, same neovim build, both gdb
and vscode-cpptools
(essentially, also gdb
) are both able to resolve and breakpoint the neovim binary at the right locations, lldb
is also able to that via the cli but for some odd reason returns verified = false
with nvim-dap.
Sounds like a lldb-vscode issue, I don't think there's anything that can be done in nvim-dap about this
Sounds like a lldb-vscode issue, I don't think there's anything that can be done in nvim-dap about this
Alright, I’ll close the issue then.
Debug adapter definition and debug configuration
Debug adapter version
lldb version 17.0.6
Steps to Reproduce
In an attempt to debug https://github.com/neovim/neovim/issues/20726, I compiled neovim nightly from source using
Resulting binary is ~18MB and seems to contain debug symbols, if I use
lldb
directly (launch or attach to pid) I can set breakpoints in the cli and they seem to resolve fine:Expected Result
If the sources resolve in
lldb
cli, I expect the breakpoints to also resolve innvim-dap
.Actual Result
However, if setting the breakpoints from
nvim-dap
,lldb
seems to reject the breakpoints (inidcated byR
in the sign column), relevant logs fromdap.log
below: