diff options
| -rw-r--r-- | doc/lispref/ChangeLog | 4 | ||||
| -rw-r--r-- | doc/lispref/debugging.texi | 11 |
2 files changed, 15 insertions, 0 deletions
diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 9d71d4b4420..cda6ed27837 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,7 @@ +2012-11-21 Glenn Morris <rgm@gnu.org> + + * debugging.texi (Profiling) [!tex]: Mention --enable-profiling. + 2012-11-20 Glenn Morris <rgm@gnu.org> * debugging.texi (Profiling): New section, in progress. diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index 4450d177896..ef1342ea289 100644 --- a/doc/lispref/debugging.texi +++ b/doc/lispref/debugging.texi @@ -849,3 +849,14 @@ The @file{elp} library offers an alternative approach. See the file You can check the speed of individual Emacs Lisp forms using the @file{benchmark} library. See the functions @code{benchmark-run} and @code{benchmark-run-compiled} in @file{benchmark.el}. + +@c Not worth putting in the printed manual. +@ifnottex +@cindex --enable-profiling option of configure +For low-level profiling of Emacs itself, you can build it using the +@option{--enable-profiling} option of @command{configure}. When Emacs +exits, it generates a file @file{gmon.out} that you can examine using +the @command{gprof} utility. This feature is mainly useful for +debugging Emacs. It actually stops the Lisp-level @kbd{M-x +profiler-@dots{}} commands described above from working. +@end ifnottex |