Repository navigation
Breakpoints ignored without binding.b at start of script #15
Description
Activity
- added a commit that references this issue
on Jul 3, 2022 - linked a pull request that will close this issueremove '-n' option when debug current file (#15) #16
on Jul 3, 2022 - added a commit that references this issue
on Jul 3, 2022 Ahhh this really messes things up for me. Basically means I have an infinite amount of steps to step over if I'm in anything remotely complex. Previously, it only stopped on my breakpoint. Now it stops right from execution. Unless I'm missing an obvious
skip to breakpointcommand...
Unless I'm missing an obvious skip to breakpoint command...
Well try
cfor continue?Reacted by OliCould you try
:lua require'dap'.continue()again or bind key:lua require'dap'.continue()yourself?Reacted by OliCould you try the lates version?
Now I have really strange behavior (but it may also be due to another update):
- I add two breakpoints and start with
:lua require'dap'.continue() - It will break on the first breakpoint I set, but then hide all the breakpoint
- When I continue again it will also break at the second (now invisible breakpoint)
- When I try to start it again it will fail to start with
couldn't connect to 127.0.0.1:38698: ECONNREFUSED
How can I debug this further?
- I add two breakpoints and start with
I am having a similar issue when I try to debug a spec file, where it will stop on the first line but then not hit any breakpoints or binding.b if I continue
I don't see anything in DapShowLogs with setting to TRACE. Is there anything else I can do to debug this?
If I don't have a
binding.bat the start of my script, all further breakpoints are just ignored and just the whole script runs:With binding.b
Without binding.b
I guess the reason is that rdbg is started with the
-nflag which means it won't break at the start:nvim-dap-ruby/lua/dap-ruby.lua
Lines 70 to 72 in 84a2831