From: Eli Zaretskii <eliz@gnu.org>
To: David Engster <deng@randomsample.de>
Cc: sva-news@mygooglest.com, 15454@debbugs.gnu.org
Subject: bug#15454: 24.3.50; The profiler does not show me all the run functions?
Date: Tue, 24 Sep 2013 23:34:35 +0300 [thread overview]
Message-ID: <83ob7igdr8.fsf@gnu.org> (raw)
In-Reply-To: <87fvsunf64.fsf@engster.org>
> From: David Engster <deng@randomsample.de>
> Date: Tue, 24 Sep 2013 22:22:11 +0200
> Cc: Sebastien Vauban <sva-news@mygooglest.com>, 15454@debbugs.gnu.org
>
> Stefan Monnier writes:
> > The profiler is based on sampling, so it can definitely "miss" things,
> > especially if we don't spend much time in them.
>
> That's my experience, too. Reducing profiler-sampling-interval usually
> helps, though.
But in any case, the profiler is not an efficient tool to study how
complex things are implemented in Emacs (or any other program).
That's what debuggers are for.
next prev parent reply other threads:[~2013-09-24 20:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 14:37 bug#15454: 24.3.50; The profiler does not show me all the run functions? Sebastien Vauban
2013-09-24 15:28 ` Stefan Monnier
[not found] ` <mailman.2795.1380036555.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.2795.1380036555.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-09-24 16:12 ` Sebastien Vauban
2013-09-24 19:13 ` Stefan Monnier
2013-09-24 20:22 ` David Engster
2013-09-24 20:34 ` Eli Zaretskii [this message]
2013-09-24 22:21 ` Stefan Monnier
2013-10-07 1:14 ` Glenn Morris
2013-09-24 16:15 ` Eli Zaretskii
[not found] ` <mailman.2798.1380039373.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.2798.1380039373.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-09-24 16:55 ` Sebastien Vauban
2013-09-24 17:44 ` Michael Heerdegen
2013-09-24 18:23 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ob7igdr8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15454@debbugs.gnu.org \
--cc=deng@randomsample.de \
--cc=sva-news@mygooglest.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.