Mention trace.el facilities in the ELisp manual

* doc/lispref/debugging.texi (Debugging): Mention the trace.el
library.

diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index cb6f6e96b022c9dea7e8a355db5a27b99c3d4fff..fbc5238dc07a4947624a48a45a9c4ade50cf3f7e 100644 (file)
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -19,6 +19,16 @@ alter its internal state.
 @item
 You can use Edebug, a source-level debugger for Emacs Lisp.
 
+@item
+@cindex tracing Lisp programs
+You can trace the execution of functions involved in the problem using
+the tracing facilities provided by the @file{trace.el} package.  This
+package provides the functions @code{trace-function-foreground} and
+@code{trace-function-background} for tracing function calls, and
+@code{trace-values} for adding values of select variables to the
+trace.  For the details, see the documentation of these facilities in
+@file{trace.el}.
+
 @item
 If a syntactic problem is preventing Lisp from even reading the
 program, you can locate it using Lisp editing commands.