-
-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 11, "invalid debug host address" when when using debugger #574
Comments
|
Yep, it does not make much sense indeed... but the command does run! however, breakpoints don't seem to work. |
@Nodragem It looks to me like you aren't actually running v2.0.0 of this extension. If you were using the latest version, the command that gets run would contain Please double check that you have the new version installed. Additionally, your launch configuration contains old fields that have been removed. Please try the new recommended minimal config: {
"name": "Launch",
"type": "godot",
"request": "launch"
} |
Worth noting that at least for me, the latest version available inside of vscode is v1.3.1, which it confirms as the latest update. |
2.0.0 is a longstanding update that hasn't been published yet, so you have to install the development build VSIX linked here: https://github.com/godotengine/godot-vscode-plugin?tab=readme-ov-file#download |
@Nodragem Are you still experiencing this issue with the released version of |
Godot version
4.2.1
VS Code version
1.85.2
Godot Tools VS Code extension version
2.0.0
System information
Windows 11
Issue description
The debugger does not work. It said it failed at running the command:
So I tried to run it in git bash to get the error message, which is:
Invalid debug host address, it should be of the form <protocol>://<host/IP>:<port>
To run the following works:
The temporary solution I am using is to modify the debugger configuration so that
port
is set to//6007
:Hope that help!
Steps to reproduce
Try to run the debugger.
The text was updated successfully, but these errors were encountered: