FR: use Debugger console for GDB comands (or at least allow them there)

[GitMensch]

currently everything in the debugger console seems to be handled as an expression to evaluate - but that's already possible using the watch pane in the debugger; other extensions therefore allow you to execute real GDB commands (so you can still "print" but also load python debug extensions, asking for inferior details, ...)

Please make a breaking change (with likely not too much people being effecting, telling them they can use the watch pane) to keep the debug console to allow the developer to directly operate with the debugger (that's what it is for).
If you feel this isn't possible then add something like "if the first word is 'gdb' (or '-exec') then we send anything afterwards top gdb)

[jreineckearm]

@GitMensch , I believe what you are asking for is already supported today. Please use > as a prefix for GDB CLI commands.
I'll keep the issue open though as I don't see this documented.

[jonahgraham]

Note that the > prefixing is a workaround to provide some basic support, it doesn't support auto-complete, multi-line, and other items.

The better option is to use openGdbConsole which launches gdb in a Terminal view and gives you a full gdb CLI. At the moment this is not supported on Windows.

Recentish gdbs (12+???) have support for new-ui, the feature that the adapter relies on to handle two communication channels (one MI for the adapter, the other CLI for the end user).

[jonahgraham]

Recentish gdbs (12+???) have support for new-ui

To clarify - new-ui is support from GDB 7.12 on Linux (and other posix environments that have real PTYs), on Windows a different communication method was added for new-ui to operate on starting around GDB 12.

LMK if you want more background here.