microsoft / microsoft/vscode-cpptools
Show some better UI hint that a compiler is not available from the dropdown of Debug C/C++ file due to a debugger being missing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Via the Debug C/C++ file button I see cl.exe and LLVM clang, but not mingw g++. I see it being added as a known compiler in the TypeScript debugger, but then something is causing it to not get used when it seems like it should be.
UPDATE: I didn't notice the logging logger.getOutputChannelLogger().appendLine(localize('debugger.path.not.exists', "Unable to find the {0} debugger. The debug configuration for {1} is ignored.", "${debuggerName}", compilerName)); -- maybe an "info/hint" entry could be added to the quick pick showing that g++ is potentially available if the user were to install the missing gdb.
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
Start at the Debug C/C++ file quick pick and trace the TypeScript debugger handling around the mentioned debugger.path.not.exists logger message. Define the hint shown when a known compiler such as mingw g++ lacks gdb, and verify that the dropdown explains why the compiler is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100