- **status**: new --> closed - **Resolution**: --> none - **Comment**:
OpenOCD can be used in "pipe" from within GDB. >From doc/openocd.texi: > A pipe connection is typically started as follows: > @example > target extended-remote | \ > openocd -c "gdb_port pipe; log_output openocd.log" > @end example > This would cause GDB to run OpenOCD and communicate using pipes > (stdin/stdout). 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 --- ** [tickets:#207] OpenOCD sends debug and warning messages to the stderr** **Status:** closed **Milestone:** 0.9.0 **Created:** Mon Sep 03, 2018 09:06 AM UTC by Roman **Last Updated:** Sat Jun 05, 2021 07:50 PM UTC **Owner:** nobody 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 --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/openocd/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
