Allow custom debug adapter type in cmake.debugConfig

[Copilot]

This change addresses item #4590

This changes visible behavior

The following changes are proposed:

• Add type property to cmake.debugConfig that, when set, skips automatic debugger detection from the CMake cache and uses the specified debug adapter directly
• Allow arbitrary additional properties in cmake.debugConfig via additionalProperties: true in the schema and an index signature on CppDebugConfiguration
• Update debugTarget() and debugCTest() in cmakeProject.ts to branch: custom type path builds a minimal base config from the target (program, cwd, name, args), then overlays the user config; otherwise falls through to existing cache-based auto-detection

The purpose of this change

cmake.debugConfig was limited to a fixed set of cppdbg/cppvsdbg properties (MIMode, miDebuggerPath, etc.). Users wanting a different debug adapter (e.g., codelldb, lldb) had no way to specify one — the adapter type was always auto-detected from the CMake cache.

Other Notes/Information

Example — using CodeLLDB instead of the auto-detected debugger:

// settings.json
{
  "cmake.debugConfig": {
    "type": "lldb",
    "sourceMap": { "/build": "${workspaceFolder}" },
    "initCommands": ["settings set target.x86-disassembly-flavor intel"]
  }
}

program, cwd, args, name, and environment are still populated automatically from the CMake target. When type is omitted, behavior is unchanged — the debugger is auto-detected from the cache as before.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Feature] Allow ability to specify custom debug launch configuration</issue_title>
<issue_description>### Request Overview

Currently cmake-tools has a hardcoded Debug Launch Configuration, e.g.:

vscode-cmake-tools/src/debug/debugger.ts

Lines 126 to 136 in 05c261e

	return {
	type: 'cppdbg',
	name: `Debug ${target.name}`,
	request: 'launch',
	cwd: path.dirname(target.path),
	args: [],
	MIMode: MIModes.lldb,
	miDebuggerPath: debuggerPath,
	program: target.path
	};
	}

And it only allows user to specify a limited number of parameters: MIMode, miDebuggerPath.

In Contrast, TestMate extension: ( https://github.com/matepek/vscode-catch2-test-adapter ) allows users to specify Debug Launch Configuration for each platform independently, as follows:
https://github.com/matepek/vscode-catch2-test-adapter/blob/master/documents/configuration/debug.configTemplate.md

Could you maybe add ability to the CMake Tools to do the same, i.e. add ability to specify debug template, which will streamline and simplify development workflow.
Additionally it would fix/workaround the issues, like: #3908

Additional Information

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Feature] Allow ability to specify custom debug launch configuration #4590

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[Omotola]

validated locally
Debugger is able to use custom settings defined in settings.json

[gcampbell-msft]

Overall I'm good with this change, just want to make sure we have clarity on some of the modifications/additions

[Omotola]

@copilot can you resolve the merge conflicts in this PR

[Copilot]

@copilot can you resolve the merge conflicts in this PR

Merge conflicts resolved in df1b9f3. Two conflicts were fixed:

• CHANGELOG.md: Kept our feature entry alongside the new entries from main (feat: add ${cmake.testEnvironment} placeholder for CTest debug configurations #4821, Add "Delete Build Directory and Reconfigure" commands #4826)
• src/cmakeProject.ts: In debugCTest(), preserved our custom type path and integrated main's new CTest ENVIRONMENT merging from feat: add ${cmake.testEnvironment} placeholder for CTest debug configurations #4821 — testInfo.environment is now combined with debugConfig.environment before calling getTargetLaunchEnvironment()

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• 40vvsblobprodwus2135.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /usr/local/bin/yarn install --frozen-lockfile (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/npm install --ignore-scripts (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/npm install typescript --no-save (dns block)
• 5azvsblobprodwus2162.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/npm install --ignore-scripts (dns block)
• 5bdvsblobprodwus2128.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/npm install --ignore-scripts (dns block)
• 78kvsblobprodwus2152.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /usr/local/bin/yarn install --frozen-lockfile (dns block)
• 7t8vsblobprodwus2168.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/npm install --ignore-scripts (dns block)
• b53vsblobprodwus2154.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /usr/local/bin/yarn install --frozen-lockfile (dns block)
• ezcvsblobprodwus2170.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/npm install --ignore-scripts (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/npm install typescript --no-save (dns block)
• km4vsblobprodwus2183.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /usr/local/bin/yarn install --frozen-lockfile (dns block)
• l7ivsblobprodwus2133.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /usr/local/bin/yarn install --frozen-lockfile (dns block)
• v41vsblobprodwus2175.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /usr/local/bin/yarn install --frozen-lockfile (dns block)
• vd2vsblobprodwus2150.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /usr/local/bin/yarn install --frozen-lockfile (dns block)
• wztvsblobprodwus2155.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /usr/local/bin/yarn install --frozen-lockfile (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)