diff options
| author | Eli Zaretskii <eliz@gnu.org> | 2018-01-13 13:53:47 +0200 |
|---|---|---|
| committer | Eli Zaretskii <eliz@gnu.org> | 2018-01-13 13:53:47 +0200 |
| commit | 5dd0e5c54d29e81c07798a124295c8c3f016d621 (patch) | |
| tree | 0573b86b2e0c38f420ad90d985f708b25fb77a33 /doc/lispref/debugging.texi | |
| parent | 97b0e41c5d9b4bd81ba35ba7d30d9bd26ec7b145 (diff) | |
| download | emacs-5dd0e5c54d29e81c07798a124295c8c3f016d621.tar.gz emacs-5dd0e5c54d29e81c07798a124295c8c3f016d621.tar.bz2 emacs-5dd0e5c54d29e81c07798a124295c8c3f016d621.zip | |
Mention trace.el facilities in the ELisp manual
* doc/lispref/debugging.texi (Debugging): Mention the trace.el
library.
Diffstat (limited to 'doc/lispref/debugging.texi')
| -rw-r--r-- | doc/lispref/debugging.texi | 10 |
1 files changed, 10 insertions, 0 deletions
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 @@ -20,6 +20,16 @@ alter its internal state. 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. |