-
Notifications
You must be signed in to change notification settings - Fork 282
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
C/C++ extension cant evoke an "externalConsole". #48
Comments
Possibly variation Microsoft/vscode#67296 and Microsoft/vscode-cpptools#2998. I was able to start up vscode-cpptools debugging with If something goes wrong, and the terminal can't be launched, then there isn't any feedback and it looks like "nothing happened" because vscode doesn't report any error (the symptom is usually the red debugging stop button lights up and then... nothing). Something is going to go "wrong" somewhat commonly, because the remote side isn't necessarily capable of launching a console. Regardless of whether the behavior changes per #45 it would be nice if there was some glaring error when the external console fails to spawn for whatever reason (including locally). |
@therealkenc oh, than you! I can figure out that. |
When
"externalConsole"
in launch.json is set false, everythig is just ok.When set true, nothing happened.
The text was updated successfully, but these errors were encountered: