Let debug breakpoint pined to the original line during debug session

[copdips]

Hello,

Suppose we add a breakpoint to the line 2, and we insert 3 blank lines before, current version of vscode will keep the breakpoint still at the line 2 which is pointed to a blank line.

original breakpoint:

line1. code1
(breakpoint here) line2. code2

add 3 blank lines before the line 2:

line1. code1
(breakpoint still here) line2. 
line3.
line4.
line5. code2

I expect to see

line1. code1
line2. 
line3
line4
(breakpoint here) line5. code2

Could you please let the breakpoint to pined to the original line code, which means if the original line of code moves, the breakpoint should go with it.

Regards

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Breakpoints stay on their original line number (do not follow statements) when code is edited during a debug run (#56398)
• Breakpoints: middle click to remove (#55323)

[weinand]

I'm not seeing the behaviour you are describing:

As you can see in the screencast, the breakpoint moves and the line number updates.

[copdips]

@weinand

thx for you rapid reponse, I cannot reproduce the issue neither.
I will raise a new issue next time I encounter it.

[copdips]

@weinand

To reproduce the issue, in fact, it's about to insert lines during debug session.

1. Set a breakpoint
2. Start a debug session and wait till the debug stops at the breakpoint
3. Insert some new line before the line where sits the breakpoint
4. Save the code
5. Stop the debug session
6. The breakpoint doesnt keep with the original code line.

[weinand]

"Live edit" while a debug session is running only works for debug extensions that support this.
The node-debugger of VS Code does not.
So node.js does not see the edited source which means it hits breakpoints in the original location (even though the breakpoint in the editor shows up in the new location). VS Code shows breakpoint with a grey ring if the breakpoint location does not match what node.js sees.

[weinand]

duplicate of #6930