Open lll123github opened 1 month ago
In the before picture, the path looks to have been corrupted in the argument for --dbgExe
. The interesting thing is that when you change to forward slashes, the argument still shows backslashes, but the corruption is not present. This appears to be an issue with the debugger side of things, but a deeper look is needed.
Environment
Bug Summary and Steps to Reproduce
Bug Summary: After selecting debug configuration, the item "command" in tasks.json is wrong which may cause error of compiling, showing in Debug Console.
Steps to reproduce:
ERROR: Unable to start debugging. Unexpected GDB output from command "-exec-run". During startup program exited with code 0xc0000135.
Expected behavior: The terminal in the vscode will output "Hello,World!"
And I found the way to solve this problem: Change
"command": "D:\\msys64\\ucrt64\\bin\\g++.exe",
to"command": "D:/msys64/ucrt64/bin/g++.exe",
And then everything goes well, and "Hello,World!" can be printed in the terminal.Configuration and Logs
c_cpp_properties.json: not created C/C++ Log Diagnostics:
C/C++ logging
Other Extensions
extensions:
Additional context
Before: After: tasks.json