vscode-cmake-tools
vscode-cmake-tools copied to clipboard
microsoft
Debugging mingw application fail if using non-cmd as integrated terminal
Brief Issue Summary
Debugging MinGW application fails if using non-cmd as an integrated terminal. I suggest vscode-cmake-tools always use cmd on windows
Example
For instance I using msys2 as integrated terminal.
"terminal.integrated.profiles.windows": {
"PowerShell": {
"source": "PowerShell",
"icon": "terminal-powershell"
},
"Command Prompt": {
"path": [
"${env:windir}\\Sysnative\\cmd.exe",
"${env:windir}\\System32\\cmd.exe"
],
"args": [],
"icon": "terminal-cmd"
},
"Git Bash": {
"source": "Git Bash"
},
"msys": {
"path": "C:\\msys64\\msys2_shell.cmd",
"args": [
"-defterm",
"-mingw64",
"-no-start",
"-use-full-path",
"-here"
]
}
},
"terminal.integrated.defaultProfile.windows": "msys",
When using "msys" as an integrated terminal, the following happens in the terminal but the debugging is not started.
When using "cmd" as an integrated terminal, the following happens and the debugging is started.
I'm not 100% sure, but I don't think that our extension has any control over the terminal used to start debugging. @WardenGnaw, would this be a feature request for the VS Code team, or is this something we'd need to address in cpptools?
This is either a mix of VS Code and MIEngine, the issue is we are using the Windows launcher for a shell that should be capable of unix styled pipes.
VS Code is running the cmd /C in MSYS, and we are assuming if we are on Windows, we should use the WindowsDebugLauncher. We will need a way in DAP to know that the terminal that is going to be used is MSYS.
