docs: reporting-issues.rst: explain how to decode stack traces
authorThorsten Leemhuis <linux@leemhuis.info>
Mon, 15 Feb 2021 17:28:57 +0000 (18:28 +0100)
committerJonathan Corbet <corbet@lwn.net>
Sun, 7 Mar 2021 00:36:52 +0000 (17:36 -0700)
commit315c4e45f10d216b371d2e2eddef228bbafaec72
treedc49263d293ad36515d5a58d3f47d489c556c6bb
parent692180345da62cb96a49fcc7808a1929634ba70b
docs: reporting-issues.rst: explain how to decode stack traces

Replace placeholder text about decoding stack traces with a section that
properly describes what a typical user should do these days. To make
it works for them, add a paragraph in an earlier section to ensure
people build their kernels with everything that's needed to decode stack
traces later.

Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
Reviewed-by: Qais Yousef <qais.yousef@arm.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
Link: https://lore.kernel.org/r/20210215172857.382285-1-linux@leemhuis.info
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Documentation/admin-guide/reporting-issues.rst