Open Xrayez opened 3 years ago
I was running into similar issues with the debugger and took a closer look. The problem is that the quit
command only tells the main loop to quit but it doesn't actually stop the GDScript VM. Like in the example above, it's quite likely that the error is encountered in the middle of a function call that will run until completion before the next iteration of the main loop.
Godot version
3.4 beta
System information
Windows 10
Issue description
While running tests and using Godot's
--debug/-d
option, passingquit/q
command to Godot's debugger does not immediately quits application if there's a script error, as the help message suggests when you passhelp/h
.The above output is from Goost, namely while working on goostengine/goost#123.
Steps to reproduce
Create a test project with main scene/script:
Then run:
Then press q and press Enter several times in succession until Godot finally quits.
The workaround: do not use
--debug
option, but then you may miss important error this way. Using Ctrl + C does not always work either while debugging this way to catch keyboard interrupt, so I have to forcefully kill Godot application, which is very inconvenient.Minimal reproduction project
cannot-quit-godot.zip