support input variables gdbpath setting

[FaFre]

I want to run the debugging inside an terminal that supports input to run gdb with sudo.

It seems like the terminal configuration is not there anymore, like stated in the readme:

Additionally you can set terminal if you want to run the program in a separate terminal with support for input. On Windows set it to an empty string ("") to enable this feature. On linux set it to an empty string ("") to use the default terminal emulator specified with x-terminal-emulator or specify a custom one. Note that it must support the -e argument.

How can I specify an external terminal instead of built-in debug console?

[WebFreak001]

ah the problem seems to be that this is an attach request, I'm not sure if we can support it, but it may be worth looking into the source code of the GDB provider to see if we can somehow implement this.

[FaFre]

I understood something wrong. I was thinking this parameter is for gdb itself, but turns out its for the program to execute.

I wanted to run the gdb command inside a terminal (maybe the vscode integrated one) to enter my password on sudo promt.

[GitMensch]

I wanted to run the gdb command inside a terminal (maybe the vscode integrated one) to enter my password on sudo promt.

The solution to the issue at hand (I've edited the issue title for that) is to use input variables in the gdbpath setting.
Can you already use ${input:pwd} there?