[LTP] [PATCH 06/10] Refactor debugging documentation

[Andrea Cervesato]

From: Andrea Cervesato <andrea.cervesato@suse.com>

The debugging documentation section explains how to debug test binaries
and to enable TDEBUG messages on tests run.
---
 doc_new/developers/debugging.rst | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/doc_new/developers/debugging.rst b/doc_new/developers/debugging.rst
index 18a4a67e9..7a4e6b2ad 100644
--- a/doc_new/developers/debugging.rst
+++ b/doc_new/developers/debugging.rst
@@ -3,8 +3,19 @@
 Debugging
 =========
 
-The new test library runs the actual test, i.e. the `test()` function in a
+This section explains some tricks which can be used to debug test binaries.
+
+Debug messages
+--------------
+
+The LTP framework currently supports ``TDEBUG`` flag test debug messages. These
+messages can be enabled using the ``-D`` test's argument.
+
+Tracing and debugging syscalls
+------------------------------
+
+The new test library runs the actual test (i.e. the ``test()`` function) in a
 forked process. To get stack trace of a crashing test in gdb it's needed to
 `set follow-fork-mode child <https://ftp.gnu.org/old-gnu/Manuals/gdb/html_node/gdb_25.html>`_.
-To trace the test, please use `strace -f` to enable tracing also for the
+To trace the test, please use ``strace -f`` to enable tracing also for the
 forked processes.

-- 
2.35.3