From: Jason Rumney <jasonr@gnu.org>
Cc: "Richard Stallman" <rms@gnu.org>,
"Emacs Bug" <emacs-pretest-bug@gnu.org>,
"Emacs Devel" <emacs-devel@gnu.org>
Subject: Re: Hang in Emacs 21.3.50
Date: 04 Dec 2002 21:57:15 +0000 [thread overview]
Message-ID: <m2of81tpl0.fsf@nyaumo.btinternet.com> (raw)
In-Reply-To: <20021204110122.84CA13FE33@server2.fastmail.fm>
"Dhruva Krishnamurthy" <seagull@fastmail.fm> writes:
> I did some further debugging using MSVC 6.0 debugger. I would like to
> report another scenerio which causes a similar HANG (infinite loop) in
> w32fns.c:w32_msg_pump()
>
> 1. I use Aspell (latest : 05.3-2 I guess)
> 2. When I do "M-x ispell-buffer", it goes to w32fns.c:w32_msg_pump() and
> gets into an infinite loop (GetMessage())
It is normal for the message pump thread to spend most of its time in
GetMessage(), and the loop is intentional. The lisp/redisplay thread
is more interesting in cases where Emacs appears to be hung.
> PS:
> Emacs is multi threaded. Am I right or am I missing something.
On MS Windows, there is the main Lisp thread, a message pump thread
(which simulates asynchronous signals and allow C-g to interrupt the
Lisp thread even when it is performing a blocking operation), and a
thread for each subprocess to handle I/O from that subprocess. The
latter thread normally exits when the subprocess exits, so the
message you see about a thread exiting is probably the thread
handling I/O for aspell, as you guessed.
The question, I think, is why does Emacs appear to hang when aspell
exits unexpectedly.
next prev parent reply other threads:[~2002-12-04 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 11:01 Hang in Emacs 21.3.50 Dhruva Krishnamurthy
2002-12-04 15:18 ` Eli Zaretskii
2002-12-04 21:57 ` Jason Rumney [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-29 11:15 Dhruva Krishnamurthy
2002-11-29 13:26 ` Kai Großjohann
2002-11-30 14:05 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2of81tpl0.fsf@nyaumo.btinternet.com \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).