andpp/mopidy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add notes about debug thread to development docs.

Browse Source
This commit is contained in:
Thomas Adamcik 2012-11-08 23:06:38 +01:00
parent a4caf998bd
commit 812733205f
2 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/changes.rst
View File

@ -88,7 +88,7 @@ backends:
- Added support for search by filename to local backend.
- Added optional background thread for debuging deadlocks. When the feature is
- Added optional background thread for debugging deadlocks. When the feature is
enabled via the ``--debug-thread`` or ``settings.DEBUG_THREAD`` a ``SIGUSR1``
signal will dump the traceback for all running threads.

11
docs/development.rst
View File

@ -284,6 +284,17 @@ Using this setup you can now run Mopidy with ``PROFILE=silent,spotify mopidy``
if you for instance want to test Spotify without any actual audio output.
Debugging deadlocks
===================
Between the numerous pykka threads and gstreamer interactions there can
sometimes be a potential for deadlocks. In an effort to make these slightly
simpler to debug ``settings.DEBUG_THREAD`` or ``--debug-thread``
can be used to turn on an extra debug thread. This thread is not linked to
the regular program flow, and it's only task is to dump traceback showing
the other threads state when we get a ``SIGUSR1``.
Writing documentation
=====================