Removing breakpoints in VSCode doesn't work

[CatarinaPBressan]

Godot version

4.1.1

VS Code version

1.83.1

Godot Tools VS Code extension version

1.3.1

System information

Windows 10

Issue description

Adding breakpoints on VSCode correctly adds breakpoints in Godot and the game stops at the correct place when running through VSCode, but removing breakpoints on VSCode doesn't work sometimes: The game pauses in the line that was previously set as a breakpoint, and the breakpoint still shows in the Godot editor.

Saving the file after removing the breakpoint sometimes removes the breakpoints, but not always.

Steps to reproduce

1. Add a breakpoint through VSCode
2. Run the game through VSCode, the game should stop at that breakpoint
3. Remove the breakpoint through VSCode
4. Run the game again through VSCode, the game should stop again at that breakpoint (at this point you can check the Godot editor and the breakpoint will still be there)

or:

1. Add a breakpoint through VSCode
2. Run the game through VSCode, the game should stop at that breakpoint
3. Remove the breakpoint through VSCode, and save the file (I usually save with the shortcut Ctrl+S)
4. Run the game again through VSCode, the game should not stop again at that breakpoint. (at this point you can check the Godot editor and the breakpoint will be removed)

[LeifintheWind]

I believe I'm having the same issue. Where adding a breakpoint in VScode works fine, but attempting to remove it then run the debug again and the breakpoint reappears!

I did notice that if the breakpoint is removed while the debugger/scene is running, it does successfully and consistently remove the breakpoint. Attempting to remove the breakpoint when the debugger/scene is not running is entirely unsuccessful for me.

[DaelonSuzuka]

@CatarinaPBressan @LeifintheWind Please post the contents of your launch.json.

[CatarinaPBressan]

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "GDScript Godot",
            "type": "godot",
            "request": "launch",
            "project": "${workspaceFolder}",
            "port": 6006,
            "debugServer": 6006,
            "address": "127.0.0.1",
            "launch_game_instance": true,
            "launch_scene": false
        }
    ]
}

[LeifintheWind]

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "GDScript Godot",
      "type": "godot",
      "request": "launch",
      "project": "${workspaceFolder}",
      "port": 6006,
      "debugServer": 6006,
      "address": "127.0.0.1",
      "launch_game_instance": true,
      "launch_scene": false
    }
  ]
}

[DaelonSuzuka]

This is a known problem with using the debugServer setting. debugServer invokes a completely different debugging protocol between between VSCode and Godot, and it's use isn't really supported (yet).

The only thing I can recommend is waiting for the new version of this extension to be published (which I hope is soon), because I've almost entirely rewritten the debugger interface and it works much better than the old one.

[mberdev]

Same issue in Godot 4.2.1. I'm indeed using debugServer. But I thought it was mandatory. How do you NOT use it? When I don't use it I got a whole other set of issues.

[DaelonSuzuka]

@mberdev

But I thought it was mandatory

Why do you think that? It's never been recommended or listed in this extension's documentation.

How do you NOT use it?

By waiting for the new version of godot-tools to be published.

When I don't use it I got a whole other set of issues.

Yes, that's why I spent most of last year rewriting the extension's debugger interface.

[bimbio]

Temporary workaround is to just type 'breakpoint' before the line you want to debug, instead of clicking the red dot thing on the side. Then when you're done with debugging just delete the line from your code.

[LeifintheWind]

Thanks for your hard work @DaelonSuzuka !

[mberdev]

@mberdev

But I thought it was mandatory

Why do you think that? It's never been recommended or listed in this extension's documentation.

How do you NOT use it?

By waiting for the new version of godot-tools to be published.

When I don't use it I got a whole other set of issues.

Yes, that's why I spent most of last year rewriting the extension's debugger interface.

To you it's obvious the difference between the several debugging systems, but to regular people it's not. We just follow tutorials titled "How to set up Godot 4.2 with VSCode" after trying to make it work by ourselves and failing.

Therefore, allow me to rephrase my question :

Is there a way to use VSCode with GDScript? i.e. a way that lets you:

• Run the game in debug mode from VSCode
• Add and remove breakpoints
• Works with the latest Godot (4.2+) Godot seems to advetrtise "yes". But then I keep stumbling upon this kind of threads that says "well it kinda works except for this and this and this"

[CatarinaPBressan]

FWIW I started using Godot 4.2 in the meantime and this is still the only issue that I've run into. The plugin is perfectly usable otherwise, and hits the other 2 bullet points.