`printf()` statements during remote debugging session don't show up in the gdbgui console

[ElectricRCAircraftGuy]

Continued from here: #332 (comment) and here: #332 (comment).

---

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Please complete the following information:

• OS:
• gdbgui version (gdbgui -v):
• gdb version (gdb -v):
• browser [e.g. chrome, safari]:
• python packages (pip freeze):

Additional context
Add any other context about the problem here.

[ElectricRCAircraftGuy]

Note that a decent work-around is to simply view all stdout output in the terminal from where I launched gdbgui on the remote machine, by adding --gdb-args="--tty=$(tty)", like this:

gdbgui --gdb-args="--tty=$(tty)"

as you describe here: https://www.gdbgui.com/faq/.

However, this is only a work-around, as it does not fix the buggy behavior which is that gdbgui will not display the std output automatically as it should--at least when launched remotely and viewed in a browser over a VPN locally.

[cs01]

This should be fixed in gdbgui v0.14.