Generic GDB remote support for non-cortexM targes

Environment

I am a developer that uses RISCV - I have also used GDB on Linux with numerous front ends. they all work, and know how to work automatically with just about all CPUs that GDB and/or the GNU tool chain supports via the "-mi" option on GDB.

HOWEVER - I found that RISCV was not supported by VSCODE
and instead VSCODE seemed to be "hard coded" for exactly CortexM series microcontrollers only.

And - when I reported this issue the basic response (paraphraed) at the time was: "It is not important enough for us to fix or resolve"

SEE: https://github.com/microsoft/vscode-cpptools/issues/11051

So my question today is this: What CPUs does VS Code support other then CortexM series.
Does it support any ESP32 chips? Does it support PIC32 - MIPS chips?

I ask this because the traditional GDB front ends all have been able to adapt to these out of the box.
I suspect VSCODE is hard coded to just CortexM series parts.

And Un-Hard coding is not interesting.

Bug Summary and Steps to Reproduce

Bug Summary:

Steps to reproduce:

1. In this environment...
2. With this config...
3. Do '...'
4. See error...

Debugger Configurations

see previous issue: https://github.com/microsoft/vscode-cpptools/issues/11051

Debugger Logs

See previous issue

Other Extensions

No response

Additional Information

No response

Read the linked vscode-cpptools issue #11051 first, then inspect the extension's existing debugger configuration and Cortex-M support. The issue provides no usable configuration, logs, or named files, so reproduction with RISC-V would need clarification. Done criteria also need definition: a supported-CPU list or generic non-Cortex-M GDB support could be intended.