unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 7722@debbugs.gnu.org, Tassilo Horn <tassilo@member.fsf.org>
Subject: bug#7722: 24.0.50; Finding this C++ header file drops emacs into a infinite loop
Date: Fri, 11 Feb 2011 20:25:06 -0500	[thread overview]
Message-ID: <8739nu82od.fsf@stupidchicken.com> (raw)
In-Reply-To: <20110204222207.GA2424@muc.de> (Alan Mackenzie's message of "Fri,  4 Feb 2011 22:22:07 +0000")

Alan Mackenzie <acm@muc.de> writes:

> It was indeed such a loop.  It was caused by a 500n jit-lock boundary
> falling in the middle of a template construct, hence the "necessity" of
> all the whitespace to reproduce the failure.
>
> Here's a putative patch for the problem.  I've refactored the offending
> function by replacing obscenely nested `if'-forms with a simple `cond'.
> I've also removed some narrowing (to the 500n limit) which should help
> jit-lock, hopefully without hurting too much elsewhere.
>
> Tassilo, would you try out the patch, please, and let me know how it
> goes.  Thanks!

Thanks.  This patch doesn't apply cleanly to the emacs-23 branch.  Do
you think we could apply it to the trunk, and just use the workaround in
the branch (some of these logic changes don't look obvious to me)?





  parent reply	other threads:[~2011-02-12  1:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24  8:28 bug#7722: 24.0.50; Finding this C++ header file drops emacs into a infinite loop Tassilo Horn
2011-01-22 20:37 ` Chong Yidong
2011-01-27  0:55   ` Chong Yidong
2011-01-30 21:23     ` Daniel Colascione
2011-02-04 22:22   ` Alan Mackenzie
2011-02-06 19:20     ` Tassilo Horn
2011-02-12  1:25     ` Chong Yidong [this message]
2011-02-13 12:20       ` Alan Mackenzie
2011-02-13 20:41         ` 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=8739nu82od.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=7722@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=tassilo@member.fsf.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).