microsoft / microsoft/vscode-cpptools

waiting for v8 protocol on stdin/stdout

Open
#2,382 7 comments 0 reactions 1 assignee View on GitHub

@WardenGnaw is already working on this.

Since Aug 10, 2018.

debugger
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Type: Debugger
Input information below

Please review existing issues and our documentation at https://github.com/Microsoft/vscode-cpptools/tree/master/Documentation prior to filing an issue.

Describe the bug

  • OS and Version:

Ubuntu 16.04

  • VS Code Version:

1.25.1

  • C/C++ Extension Version:

0.17.7

  • Other extensions you installed (and if the issue persists after disabling them):

cmake tools 1.1.1

  • A clear and concise description of what the bug is.

Unable to 'cout' to the console.
instead there is this message in the extension console:
"waiting for v8 protocol on stdin/stdout"

I tried to google this message and find informations on the web, but maybe my knowledge is not enough.

Here is the main.cpp file from cmake : quick start

#include

int main(int, char**) {
std::cout << "Hello, world!\n";
}

To Reproduce
Steps to reproduce the behavior:

Installed last version of cmake
installed last version of clang
installed last version of studio code
delete all studio code user settings
launch vscode studio
installed last version of plugin cpptools
installed last version of cmake tools
change user settings to the path of cmake
change user settings to the path of clang
restart vs code studio
create a new folder 'test'
palette: cmake : quick start with this settings : gcc 5.4, Executable, project title 'test'.
Press button to build
Press button to debug
Open extension console, the message "waiting for v8 protocol on stdin/stdout" is displayed, but no "Hello World" message.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.