Traces » History » Revision 4
Revision 3 (Jaroslav Kysela, 2015-06-02 10:58) → Revision 4/13 (Jaroslav Kysela, 2015-06-02 11:15)
h1. Traces - verbose debugging
It is quite usuall that a developer asks you to provide more verbose logs using the trace (verbose logs for development) tracing subsystem which tvheadend includes. If you see --trace <comma_separated_list_of_subsystems> you need to follow this.
Compile tvheadend using --enable-trace option for the configure script see [[Building]] to compile tvheadend directly from sources. The traces are enabled by default, but packages - except debug versions - disable this functionality.
The first way to enable traces is from the command-line options (to specify the log file and all subsystems to debug), like:
<pre>
./build.linux/tvheadend -l /tmp/tvheadend.log --trace htsp,subscription,pat,pmt,bat
</pre>
The second way is to use the debugging tab in the configuration (this settings is not preserved):
!debugging.png!
It is quite usuall that a developer asks you to provide more verbose logs using the trace (verbose logs for development) tracing subsystem which tvheadend includes. If you see --trace <comma_separated_list_of_subsystems> you need to follow this.
Compile tvheadend using --enable-trace option for the configure script see [[Building]] to compile tvheadend directly from sources. The traces are enabled by default, but packages - except debug versions - disable this functionality.
The first way to enable traces is from the command-line options (to specify the log file and all subsystems to debug), like:
<pre>
./build.linux/tvheadend -l /tmp/tvheadend.log --trace htsp,subscription,pat,pmt,bat
</pre>
The second way is to use the debugging tab in the configuration (this settings is not preserved):
!debugging.png!