envFile values not propagated to Debugger

Smit-tay commented 4 years ago

Type: Debugger

Describe the bug

Linux - Fedora 31 Linux 5.5.11-200.fc31.x86_64 #1 SMP Mon Mar 23 17:32:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

VS Code Version:

Version: 1.43.2 Commit: 0ba0ca52957102ca3527cf479571617f0de6ed50 Date: 2020-03-24T07:52:11.516Z Electron: 7.1.11 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Linux x64 5.5.11-200.fc31.x86_64
C/C++ Extension Version:

C/C++ for Visual Studio Code Change Log Version 0.27.0-insiders5: March 26, 2019
Other extensions you installed (and if the issue persists after disabling them):

N/A
A clear and concise description of what the bug is: envFile is not propogated to the debugee. This can be demonstrated via the following launch.json entry: { "name": "(Debug) Test envFile", "type": "cppdbg", "request": "launch", // any debuggable application will suffice, we don't really debug it "program": "${workspaceFolder}/build/test", // because we stop on entry "stopAtEntry": true, "linux": { "internalConsoleOptions": "openOnSessionStart", "MIMode": "gdb", "envFile": "/home/jack/test_envFile.env", "setupCommands": [ { "description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true }, ], }, "windows": { //"envFile": "C:\PATH_TO\test_envFile.env" }, "osx": { // Does anybody seriously develop under osx ? }, "externalConsole": false, },

Create a file named "test_envFile.env" which contains the following:

UNIQUE_VARIABLE="test1":"test2":"quoted string":unquoted string

after launching - when the debugger stops on entry - issue this in the debug console: "-exec show env"

Then copy all output, paste into your favorite editor, and search for UNIQUE_VARIABLE

RonaldinhoL commented 4 years ago

in my case both "environment" and "envFile" not working .

Smit-tay commented 4 years ago

only environment is fixed in the latest version of the extension. (Version 0.27.0: March 30, 2020)

Apparently, somehow "envFIle" is handled significantly differently than "environment" (go figure).

Smit-tay commented 4 years ago

Please fix. This is killer bug

microsoft / vscode-cpptools