From: David Z Maze <dmaze@MIT.EDU>
To: ding@gnus.org
Subject: Re: how to know what emacs is doing..
Date: Thu, 21 Jun 2007 10:20:32 -0400 [thread overview]
Message-ID: <y68odj9crtb.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <loom.20070621T112925-600@post.gmane.org> (francois.lagarde@gmail.com's message of "Thu\, 21 Jun 2007 09\:38\:20 +0000 \(UTC\)")
lagarde <francois.lagarde@gmail.com> writes:
> I changed my emacs version to GNU Emacs 22.0.91.1. Sometimes, my emacs
> process uses the whole cpu and cant decrease. This behavior occures
> even if I edit a text and doesnt seem to result to a special command
> call.
>
> So my question is to know if there is a way to know what emacs is
> currently doing, and what are these most consuming threads.
Well, very basic Emacs debugging is to (setq debug-on-error t) and then
hit C-g when it appears to freeze up. That will show you the current
evaluation stack, which might be a little counterintuitive, but it does
in fact tell you what Emacs is doing. Unless Emacs 23 has changed (and
I definitely would have expected to hear on this list) it's not
multithreaded at all.
It looks like you found this list via gmane; you should probably be
aware that it's the developers' list for the Gnus mail reader, which is
part of Emacs but not Emacs itself. The broader Usenet gnu.emacs.help
newsgroup might be a better place for general Emacs questions.
--dzm
next prev parent reply other threads:[~2007-06-21 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 9:38 lagarde
2007-06-21 14:20 ` David Z Maze [this message]
2007-06-21 17:02 ` Reiner Steib
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=y68odj9crtb.fsf@contents-vnder-pressvre.mit.edu \
--to=dmaze@mit.edu \
--cc=ding@gnus.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).