Add Launch Configuration Defaults for C/C++ debugger (similar to CodeLLDB)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Read the linked CodeLLDB Launch Configuration Defaults documentation and compare it with the extension's launch.json and C_Cpp.default settings. Trace how cppdbg launch and attach configurations are processed. Done means user, workspace, and folder defaults are applied before each configuration and can be overridden per configuration.
Written by the indexing model from the issue text.
Description
Feature Request
CodeLLDB supports Launch Configuration Defaults at multiple levels (user, workspace, and folder), allowing common debugger settings to be defined once and inherited by all launch.json entries (e.g. initCommands, preRunCommands, postRunCommands, pretty-printer setup, target/platform hints, etc.). See the full list here.
vscode-cpptools currently lacks this capability, which forces duplication of complex base configurations within a project.
Please add simple Launch Configuration Defaults, for example: C_Cpp.default.cppdbg.launch and C_Cpp.default.cppdbg.attach (optionally VS debugger equivalents), applied before launch.json and overridable per configuration.
I understand that proper configuration inheritance inside launch.json would be a more general VS Code-level solution, but it is unlikely to be implemented anytime soon. This proposal solves the problem now, in a very simple way, and follows an already proven model.
A typical use case is shipping a workspace file in the repository with complex base debugger setup (pretty printers, init commands, debugger tuning), while users only customize launch.json configs with parameters such as args and cwd.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 58
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.
More from microsoft/vscode-cpptools
-
bug Language Service regression
microsoft/vscode-cpptools#14795 · 1 comment · 1 assignee ·
-
bug Language Service parser
microsoft/vscode-cpptools#14794 · 1 comment · 1 assignee ·
-
more info needed
microsoft/vscode-cpptools#14793 · 2 comments · 1 assignee ·
-
more info needed
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/vscode-cpptools#14787 · 1 comment · 1 assignee ·
-
[Bug] cpptools fails to start on Ubuntu ARM64 due to missing execute permissions on shared libraries Openbug fixed Language Service regression
microsoft/vscode-cpptools#14779 · 1 comment · 1 assignee ·
All issues in microsoft/vscode-cpptools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vercel-labs/just-bash#464 ·
-
looksLikeSlug() is ASCII-only, so non-Latin entity slugs (e.g. Korean) skip exact match and collapse Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
TanStack/tanstack.com#1293 ·