Remote debugging output is polluted by bashdb messages

[Ashark]

When using remote run target, as described in documentation, viewing the stdout in console is rather impossible due to mixed ouptut from bashdb itself.

Running the same script locally does not have such problem. The Console tab rightfully only prints the starting command and the output of the script itself.

Can this be fixed?

Software versions:
BashSupport Pro plugin: 4.5.1.251 (Jan 17, 2025).

Local machine: Arch Linux, bash 5.2.37.
Remote machine: Arch Linux, bash 5.2.37.

I also tried with bash4, and with zsh. It does not change the situation.

[jansorg]

Thanks for reporting!
Unfortunately, this is tricky to fix (if possible at all).
The local environment allows for more control about the debugger's input and output streams. I'll investigate again if there's perhaps a new way to handle this for remote debugging.