You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if setting a breakpoint before starting the debugger is a supported use-case, but I didn't find anything in the documentation that suggested it wasn't.
This could be stated more clearly or, alternatively, the debugger could be implicitely started when trying to set the first breakpoint.
Expected
The debugger stops on the breakpoint
Actual
The debugger continues to completion.
Notes
When swapping steps 2 and 3, so starting the debugger first, THEN setting a breakpoint, we get the actual behaviour.
Looking at the logs, it seems like all the vim parameters are sent to the debugger only on start, but breakpoints are allowed to be defined before that.
Reproduction
path_maps
and disablebreak_on_stop
I don't know if setting a breakpoint before starting the debugger is a supported use-case, but I didn't find anything in the documentation that suggested it wasn't.
This could be stated more clearly or, alternatively, the debugger could be implicitely started when trying to set the first breakpoint.
Expected
The debugger stops on the breakpoint
Actual
The debugger continues to completion.
Notes
When swapping steps 2 and 3, so starting the debugger first, THEN setting a breakpoint, we get the actual behaviour.
Looking at the logs, it seems like all the vim parameters are sent to the debugger only on start, but breakpoints are allowed to be defined before that.
Some debugging with the following command follows
Start before Breakpoint
And the breakpoint is honoured.
Breakpoing before Start
And the breakpoint is not honoured, as the local path has not been replaced.
The text was updated successfully, but these errors were encountered: