GDB remote stdio

[Francesco Stefanni (FStefanni)]

Hi,

I am not sure if this is an issue of this extension, or a misconfiguration of my setup, anyway...

I am debugging from Linux x64 to Linux Arm, with remote gdb.
My launch config is the following:

{
    "name": "Debug basicTest",
    "type": "cppdbg",
    "request": "launch",
    "program": "${workspaceRoot}/build_arm/basicTest/basicTest/bin/basicTest",
    "args": [],
    "stopAtEntry": true,
    "cwd": "${workspaceRoot}",
    "environment": [],
    "externalConsole": false,
    "MIMode": "gdb",
    "miDebuggerPath": "gdb-multiarch",
    "setupCommands": [
        {
            "description": "Enable pretty-printing for gdb",
            "text": "-enable-pretty-printing",
            "ignoreFailures": true
        },
        {
            "description": "Setup remote debugging",
            "text": "target extended-remote | sshpass -p superpassword ssh -T debian@192.168.10.1 gdbserver --multi --once -",
            "ignoreFailures": false
        },
        {
            "description": "Send program to remote",
            "text": "remote put ${workspaceRoot}/build_arm/basicTest/basicTest/bin/basicTest /tmp/basicTest",
            "ignoreFailures": false
        },
        {
            "description": "Set program to remote",
            "text": "set remote exec-file /tmp/basicTest",
            "ignoreFailures": false
        }
    ]
}

So far, so good: it runs, and works properly.
The issue is about the stdio (and maybe stderr) of the debugged program:

• In VS code I am unable to see it!
• Instead, if I run the same commands directly in gdb, I have the "Hello world" print (and that's why I am using this way of running gdb server: to have the prints the remote target does).

For example, this is part of the gdb output when run in a shell by hand:

Reading /usr/lib/debug//lib/arm-linux-gnueabihf/629ed8ae35275b1ac80b20cfedd7ad00109548.debug from remote target...
Reading /usr/lib/debug/lib/arm-linux-gnueabihf//629ed8ae35275b1ac80b20cfedd7ad00109548.debug from remote target...
Reading target:/usr/lib/debug/lib/arm-linux-gnueabihf//629ed8ae35275b1ac80b20cfedd7ad00109548.debug from remote target...
Hello world!
[Inferior 1 (process 467) exited normally]
(gdb)

Conversely, in VS code, I have the various "Reading..." messages in the Debug Console, but no "Hello world!" (nor in vs code terminal).

Is there a way to get the missing output?
Or could this be a bug of vscode-cpptools extension?

Thank you for any help.
Regards.