docs/gst/running.xml: GStreamer supports more debuggins levels

https://bugzilla.gnome.org/show_bug.cgi?id=679008
This commit is contained in:
Javier Jardón 2012-06-28 03:56:12 +09:00 committed by Tim-Philipp Müller
parent e6d6cbf5e3
commit b348f1daad

View file

@ -95,7 +95,7 @@ to print out different types of debugging information to stderr.
<para>
The variable takes a comma-separated list of "category_name:level" pairs
to set specific levels for the individual categories.
The level value ranges from 0 (nothing) to 5 (LOG).
The level value ranges from 0 (nothing) to 9 (MEMDUMP).
<variablelist>
<varlistentry>
@ -148,6 +148,40 @@ these include setup, teardown, change of parameters, ...
Logs all log messages. These are messages for events
that happen repeatedly during an object's lifetime;
these include streaming and steady-state conditions.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>6 - <option>FIXME</option></term>
<listitem>
<para>
Logs all fixme messages. Fixme messages are messages that indicate that something
in the executed code path is not fully implemented or handled yet. The purpose
of this message is to make it easier to spot incomplete/unfinished pieces of
code when reading the debug log.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>7 - <option>TRACE</option></term>
<listitem>
<para>
Logs all trace messages. These messages for events
that happen repeatedly during an object's lifetime such as the
ref/unref cycles.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>9 - <option>MEMDUMP</option></term>
<listitem>
<para>
Log all memory dump messages. Memory dump messages are used to log
(small) chunks of data as memory dumps in the log. They will be displayed
as hexdump with ASCII characters.
</para>
</listitem>
</varlistentry>
@ -167,7 +201,7 @@ For example, setting <envar>GST_DEBUG</envar> to
<para>
To get all possible debug output, set
<envar>GST_DEBUG</envar>
to <option>*:5</option>
to <option>*:9</option>
</para>
</formalpara>