Launch gdbtarget fails at the workspace level (VSC-1552)

[i400s]

OS

Windows

Operating System version

Debian Trixie

Visual Studio Code version

1.96.2

ESP-IDF version

v5.5-dev-1050-gb5ac4fbdf9

Python version

3.12.8

Doctor command output

report.txt

Extension

{"message":"${workspaceFolder}/build/project_description.json doesn't exist.","stack":"Error: ${workspaceFolder}/build/project_description.json doesn't exist.\n\tat /dist/extension.js:2:1418922\n\tat new Promise ()\n\tat fe (/dist/extension.js:2:1418878)\n\tat jc.resolveDebugConfiguration (/dist/extension.js:2:1748101)\n\tat file:///out/vs/workbench/api/node/extensionHostProcess.js:122:99660","level":"error","timestamp":"2025-01-04T11:32:08.582Z"}

Description

When a debug gdbtarget launch configuration is set at the workspace level .code-workspace it fails to run with no errors or messages shown.

Having a launch.json file in multiple application directories causes them to all be displayed within the debug dropdown. This seems fine as they all launch. Having a global launch for the workspace (that should run using the ESP-IDF Current project) only seems to work with "type": "espidf" and not with the "type": "gdbtarget".

To make sure the issue wasn't the multi folder/project workspace that I normally use I created clean environment and a new workspace based on the blink example. I then added a .code-workspace file that pointed to . only.

{
	"folders": [
		{
			"path": "."
		}
	],
	"settings": {
		"idf.port": "/dev/ttyACM1",
		"idf.flashType": "UART",
		"idf.openOcdDebugLevel": 2,
		"idf.openOcdLaunchArgs": [
			"-c adapter serial 40:4C:CA:43:1C:AC"
		],
		"idf.openOcdConfigs": [
			"board/esp32c6-builtin.cfg"
		],
	},
	"launch": {
		"version": "0.2.0",
		"configurations": [
			{
			  "type": "gdbtarget",
			  "request": "attach",
			  "name": "Eclipse CDT GDB Adapter"
			},
			{
			  "type": "espidf",
			  "name": "Launch",
			  "request": "launch"
			}
		],
	},
}

This failed to launch the workspace version of gdbtarget while being able to launch the espidf version at the workstation level and also able to launch the folder level of both gdbtarget and espidf.

Thanks in advance.

Debug Message

none

Other Steps to Reproduce

No response

I have checked existing issues, online documentation and the Troubleshooting Guide

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.

[brianignacio5]

The issue here it seems that launch configurations defined in .code-workspace doesn't define which folder to use for debugging when launching the debug session.

The question is then, how to identify which folder to use for debug in this case? We have a ESP-IDF: Pick a Workspace Folder command to select the current workspace folder to use which is used in espidf configuration but we could also make it available here.