OpenOCD sends debug and warning messages to the stderr.
Expected result: Debug and warning, info messages should be sent to stdout. Error messages should be sent to the stderr.
Actual result: All messages (debug, warning, error) messages are sent to the stderr
OpenOCD can be used in "pipe" from within GDB.
From doc/openocd.texi:
To avoid mixing LOGs with GDB communication, all OpenOCD output is by default sent to stderr.
Nevertheless it can be redirected wherever you want with the "log_output" command.
If you want it on stdout you can, on Linux, add on commandline "-c log_outupt /dev/stdout"
For me this ticket is not valid and should be closed
OpenOCD can be used in "pipe" from within GDB.
From doc/openocd.texi:
To avoid mixing LOGs with GDB communication, all OpenOCD output is by default sent to stderr.
Nevertheless it can be redirected wherever you want with the "log_output" command.
If you want it on stdout you can, on Linux, add on commandline "-c log_outupt /dev/stdout"
For me this ticket is not valid and should be closed as
Do you know what the equivalent is on Windows?
Last edit: Tommy Murphy 2021-06-18
I always forget about Windows!
Have you tried either "CON" or "CON:" ?
https://superuser.com/questions/241272/windows-how-to-redirect-file-parameter-to-stdout-windows-equivalent-of-dev-s
If it doesn't work we would need adding hooks in OpenOCD to intercept the string "/dev/stdout" or "stdout" and redirect the log.