review debugging env vars
@ensonic
Submitted by Stefan Kost Link to original bug (#733188)
Description
Current debug-log env vars
GST_DEBUG_FILE (defaults to stderr)
when not set log to stderr, when set points to path for the debug log
GST_DEBUG_COLOR_MODE (defaults to color) (deprecated)
when set use ansi color codes, otherwise plain text
GST_DEBUG_NO_COLOR ("on", "auto", "off", "disable", "unix")
on = auto: platform specific color codes
off = disabled: no color codes
unix = force ansi
Proposed env vars
GST_DEBUG_CHANNEL (defaults to stderr)
stderr
fd://stderr, fd://stdout
file:///path/to/file (or /path/to/file , file)
tcp://<ip>
:<port>
(or just <ip>
:<port>
)
mem://<size>
Log to the given channel.
Alternative names GST_DEBUG_{STREAM,OUT,METHOD,....}
GST_DEBUG_FORMAT (default to text/auto-color)
text/plain (plain text)
text/auto-color (platform specific color codes)
text/ansi (ansi color coded)
binary/ctf (see babeltrace (Common Trace Format (CTF), e.g. used by lttng)
These could be sort-of mime-types.
We also could discuss if we just want to have one at a time, or even allow multiple pairs. The ater makes it tricky for the variables though.
Another alternative would be to merge CHANNEL+FORMAT as a uri:
GST_DEBUG_OUT=fd://stderr#format=text/plain&option1=value&option2=value
Version: 1.x