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

docs: Formatting

Browse Source
This commit is contained in:
Stein Magnus Jodal 2012-11-08 23:15:13 +01:00
parent f5dc6d6069
commit c23baf859e
2 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/changes.rst
View File

@ -89,8 +89,9 @@ backends:
- Added support for search by filename to local backend.
- 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.
enabled via the ``--debug-thread`` option or
:attr:`mopidy.settings.DEBUG_THREAD` setting a ``SIGUSR1`` signal will dump
the traceback for all running threads.
**Bug fixes**

10
docs/development.rst
View File

@ -287,12 +287,12 @@ 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
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``.
simpler to debug the setting :attr:`mopidy.settings.DEBUG_THREAD` or the option
``--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