Standard error not printed when using PipeTransport

Type: Debugger

• OS and Version: ( local ) Windows_NT x64 10.0.18363 & ( remote ) Red Hat Enterprise Linux Workstation release 7.4 (Maipo)
• VS Code Version: Version: 1.44.2
• C/C++ Extension Version: 0.27.0

Environment : VSCode from local computer, connection trough remote-ssh to a Linux computer able to run VSCode then using pipeTransport to a dedicated machine to work on, where vscode can't be launch trough remote-ssh ( older os ).

When debugging with pipe transport, message to standard error are not displayed, although received. It's also reproducible with gdb command -exec p printf(stderr,"stderr")

To Reproduce
main.c

#include <stdio.h>

int main(int argc, char *argv[])
{
    fprintf(stdout,"stdout\n");
    fprintf(stderr,"stderr\n");
    return 0;
}

launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(gdb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/a.out",
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}",
            "externalConsole": false,
            "MIMode": "gdb",
            "pipeTransport": {
                "pipeCwd": "${workspaceFolder}",
                "pipeProgram": "ssh",
                "pipeArgs": [
                    "dedicated"
                ],
                "debuggerPath": "/usr/bin/gdb"
            },
            "logging": {
                "engineLogging": true,
            }
        }
    ]
}

Steps to reproduce the behavior:

1. Compile the program
2. Launch VSCode debugger
3. Look for lines in the debug console

1: (7622) STDERR: stderr ---------------------> Program printed to stderr, GDB received it
1: (7626) ->^running ---------------------> Didn't display it
1: (7626) ->*running,thread-id="all"
1: (7626) ->(gdb)
1: (7626) ->stdout ---------------------> Program printed to stdout, GDB received it
stdout ---------------------> Did display it

Reproduce the issue with main.c and the launch.json pipeTransport configuration, then inspect the debugger output path for messages received on standard error. Compare the displayed stderr and stdout output, and consider the issue done when stderr from both program execution and the GDB printf command appears in the debug console.