From 5dd0e5c54d29e81c07798a124295c8c3f016d621 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sat, 13 Jan 2018 13:53:47 +0200 Subject: [PATCH] Mention trace.el facilities in the ELisp manual * doc/lispref/debugging.texi (Debugging): Mention the trace.el library. --- doc/lispref/debugging.texi | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index cb6f6e96b02..fbc5238dc07 100644 --- 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. -- 2.39.5