microsoft / microsoft/vscode-cpptools
[Feature Request] Support RunInTerminal Environment Variables
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
After updating the extension to 0.27.0 I am unable to debug C++ any more. The debugging works fine in version 0.26.3. I get error: "During startup program exited with code 0xc0000135"
My guess is that the updated extension ignores the "environment" setting from launch.json, as update to the Path variable is no longer visible in the terminal command when I invoke the debugging session, it was visible for 0.26.3.
I am compiling using MinGW 5.3.0 included in Qt 5.9.6 and using GDB from the same toolchain.
Likely not related to issue #5221, as my problem only applies to the new version
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the C++ debugging failure in VS Code extension 0.27.0 with the launch.json environment setting, then compare it with 0.26.3. Trace the RunInTerminal handling and verify that the Path value is passed into the terminal command so the MinGW/GDB session starts successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100