From: Eli Zaretskii <eliz@gnu.org>
To: acm@muc.de, 10664@debbugs.gnu.org
Subject: bug#10664: 24.0.93; JIT font-lock infloops in a C file
Date: Tue, 07 Feb 2012 19:30:17 +0200 [thread overview]
Message-ID: <83ehu6blg6.fsf@gnu.org> (raw)
In-Reply-To: <83wr7zc2r2.fsf@gnu.org>
> Date: Mon, 06 Feb 2012 19:04:17 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 10664@debbugs.gnu.org
>
> > Date: Mon, 6 Feb 2012 11:09:57 +0000
> > Cc: 10664@debbugs.gnu.org
> > From: Alan Mackenzie <acm@muc.de>
> >
> > I got something similar for this socket.c. I load it into emacs -Q, then
> > start scrolling downwards, a page at a time. The first five scrolls are
> > fine. Then it hangs on the sixth.
> >
> > However, typing C-g (maybe twice) frees it up, and it does the scroll.
> > Careful perusal reveals that the fontification is incomplete. From now
> > on, most key sequences must be followed by C-g to perform their commands.
> > ;-(.
> >
> > Did you actually try C-g when your session hung?
>
> I'm quite sure I did. But that was on Windows, where C-g is less
> powerful than on Posix platforms (since keyboard input is not
> interrupt driven). So it could be that what you can interrupt on
> GNU/Linux, I cannot on Windows.
I'm now absolutely sure this is the case: the offending code runs with
inhibit-quit set, and that prevents Emacs on Windows from interrupting
that code. I know because attaching GDB and using the debugger to set
inhibit-quit to nil breaks the vicious circle and let me salvage my
session without killing Emacs.
Btw, this time the problem happened with main.c from the recent Gawk
4.0.0h pre-release.
next prev parent reply other threads:[~2012-02-07 17:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 18:23 bug#10664: 24.0.93; JIT font-lock infloops in a C file Eli Zaretskii
2012-02-05 18:18 ` Eli Zaretskii
2012-02-06 11:09 ` Alan Mackenzie
2012-02-06 14:39 ` Stefan Monnier
2012-02-06 17:04 ` Eli Zaretskii
2012-02-07 17:30 ` Eli Zaretskii [this message]
2012-02-07 19:20 ` Alan Mackenzie
2012-02-07 20:58 ` Eli Zaretskii
2012-02-07 21:34 ` Alan Mackenzie
2012-02-07 23:39 ` Stefan Monnier
2012-02-08 11:47 ` Alan Mackenzie
2012-02-08 17:49 ` Eli Zaretskii
2012-02-08 19:28 ` Stefan Monnier
2012-02-10 11:28 ` Alan Mackenzie
2012-02-12 20:57 ` Eli Zaretskii
2012-02-14 5:42 ` Chong Yidong
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=83ehu6blg6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10664@debbugs.gnu.org \
--cc=acm@muc.de \
/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).