Open lgmcode opened 5 years ago
You can change the filtering of stdout in the debug console by using the setting "filterStdout": false
to see if you get output. I think by default its set to true
@pieandcakes Thanks for your advice. I just tried to add "filterStdout": false
to the remote debugging configuration in my launch.json
, but saddly nothing is changed, the stdout stays where it was. I also tried to add "filterStdout": false
to the local debugging configuration, still nothing different happened. It seems this setting has no effect. Am I still missing something?
Type: Debugger
Describe the bug
I'm doing remote debugging on Ubuntu 16.04 for a target board running qnx7, everything works well, except that the stdout of my program is shown in the debug console instead of the terminal as local debugging which looks more comfortable.
A code sample:
When debug locally, it's fine, debug console shows
and terminal shows
But if I use qnx-gdb to debug remotely, everything goes to debug console
and the terminal only has
I searched for the manual of gdb and found https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Stream-Records.html#GDB_002fMI-Stream-Records, according to which I know that the prefix character '@' means the following string is a target output, while it is not parsed by this extension, I thought.
Debugging the program in command line shows the different output of the two gdbs
With local gdb
with qnx gdb
The main difference and which I think is also the reason of the problem is that the target output in qnx gdb is quoted and has a prefix character '@' while local gdb just output the raw string. Maybe this extension does not parse this output format and leave the stdout in the debug console. Is this a bug?