Debugger may cause system errors when command initiative is left in the console

[vincedani]

Hi there!

I would like to debug a C++ application (may not be important), so a new console is created as cppdbg: name....
The problem is, if I write a command initiative into that console, then start the debugger, it fails.

Like

$ ^C  /usr/bin/env /bin/sh /tmp/Microsoft-MIEngine-Cmd-2bopttgv.y62
bash: :s^C  /usr/bin/env /bin/sh /tmp/Microsoft-MIEngine-Cmd-2bopttgv.y62 : substitution failed

A bigger problem there if e.g. a remove command initiative is there:

$ rm -rf ./build /usr/bin/env /bin/sh /tmp/Microsoft-MIEngine-Cmd-2bopttgv.y62
rm: cannot remove '/usr/bin/env': Permission denied
rm: cannot remove '/bin/sh': Permission denied

If somebody started the IDE with root privileges, then this would cause an uncomfortable surprise.

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.15.2 (user setup)
• OS Version: Ubuntu 20.04

[weinand]

/extCpp

[vscode-triage-bot]

It looks like this is caused by the C++ extension. Please file it with the repository here. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.

Happy Coding!