Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
38a2f917
Commit
38a2f917
authored
Nov 20, 2012
by
Glenn Morris
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* doc/lispref/debugging.texi (Profiling) [!tex]: Mention --enable-profiling.
parent
1b3b7caa
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
15 additions
and
0 deletions
+15
-0
doc/lispref/ChangeLog
doc/lispref/ChangeLog
+4
-0
doc/lispref/debugging.texi
doc/lispref/debugging.texi
+11
-0
No files found.
doc/lispref/ChangeLog
View file @
38a2f917
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.
...
...
doc/lispref/debugging.texi
View file @
38a2f917
...
...
@@ -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
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment