Describe the bug
Using neovim, debugging itself works all fine, unless I restart the session (using nvim-dap extension with require('dap').restart()). When I restart the session, it hits the first breakpoint and kind of detaches(?): i.e. I can click step over and it will just do nothing (although indicating that execution is not stopped at the breakpoint anymore). I have to click "terminate session" twice to see [Process terminated] in the terminal. I tried the same launch.json in vscode and restarting works fine
To Reproduce
Steps to reproduce the behavior:
Have a file like test.js
const a = 1;
console.log(a);
const b = 2;
console.log(b);
Describe the bug Using neovim, debugging itself works all fine, unless I restart the session (using
nvim-dap
extension withrequire('dap').restart()
). When I restart the session, it hits the first breakpoint and kind of detaches(?): i.e. I can click step over and it will just do nothing (although indicating that execution is not stopped at the breakpoint anymore). I have to click "terminate session" twice to see [Process terminated] in the terminal. I tried the same launch.json in vscode and restarting works fineTo Reproduce Steps to reproduce the behavior:
test.js
And launch config:
dap.restart()
, hit the breakpoint, click Step Over and observe session detaching...Log File Log from
nvim-dap
, includes: start the session, hitting breakpoint, stepping over, restarting, hitting breakpoint, stepping over, terminating, terminating again.loadedSource
event andstackTrace
commands removed as too lengthyVersion I built
dapDebugServer
from the latest commitAdditional context Sorry if
nvim-dap
issue, but I use like the most basic config