From 283362526655c8aded0b5ba1f5f1f58c7213cf4e Mon Sep 17 00:00:00 2001 From: Max Kellermann Date: Tue, 6 Nov 2018 22:38:34 +0100 Subject: [PATCH] doc/user.rst: more markup --- doc/user.rst | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/user.rst b/doc/user.rst index 50e4e376b..23ed5bcc9 100644 --- a/doc/user.rst +++ b/doc/user.rst @@ -967,7 +967,12 @@ All :program:`MPD` crashes are bugs which must be fixed by a developer, and you A crash bug report needs to contain a "backtrace". -First of all, your :program:`MPD` executable must not be "stripped" (i.e. debug information deleted). The executables shipped with Linux distributions are usually stripped, but some have so-called "debug" packages (package mpd-dbg or mpd-dbgsym on Debian, mpd-debug on other distributions). Make sure this package is installed. +First of all, your :program:`MPD` executable must not be "stripped" +(i.e. debug information deleted). The executables shipped with Linux +distributions are usually stripped, but some have so-called "debug" +packages (package :file:`mpd-dbgsym` or :file:`mpd-dbg` on Debian, +:file:`mpd-debug` on other distributions). Make sure this package is +installed. If you built :program:`MPD` from sources, please recompile with Meson option ":code:`--buildtype=debug -Db_ndebug=false`", because this will @@ -980,4 +985,5 @@ You can extract the backtrace from a core dump, or by running :program:`MPD` in gdb --args mpd --stdout --no-daemon --verbose run -As soon as you have reproduced the crash, type "bt" on the gdb command prompt. Copy the output to your bug report. +As soon as you have reproduced the crash, type ":command:`bt`" on the +gdb command prompt. Copy the output to your bug report.