From: Daniel Colascione <dan.colascione@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
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: Sun, 30 Jan 2011 13:23:35 -0800 [thread overview]
Message-ID: <4D45D6D7.1000504@gmail.com> (raw)
In-Reply-To: <87k4hrcgi4.fsf@stupidchicken.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/26/11 4:55 PM, Chong Yidong wrote:
> Chong Yidong <cyd@stupidchicken.com> writes:
>
>>> 1. emacs -Q bug.hpp
>>> 2. emacs loops infinitely using 100% CPU resources
>>>
>>> The offending file is that (according to the original reporter, the
>>> spaces and empty lines are needed):
>>
>> I can reproduce this (file attached for convenience). Alan, could you
>> take a look? Looks like a loop in c-forward-<>-arglist-recur:
>
> In the meantime, I have added the following hack/workaround to the
> emacs-23 branch, which seems to break the loop. Let me know if you find
> a fix that's safer (since we are well into the 23.3 pretest).
Incidentally, I can't reproduce the problem with the trunk cc-mode.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
iEYEARECAAYFAk1F1soACgkQ17c2LVA10VvtFACgi2KuRCq9m15aDx44xGtVTYGB
Z3AAnjuVGnWv1P6gz4vItI5HOoSiVcMw
=Emh5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-01-30 21:23 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 [this message]
2011-02-04 22:22 ` Alan Mackenzie
2011-02-06 19:20 ` Tassilo Horn
2011-02-12 1:25 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D45D6D7.1000504@gmail.com \
--to=dan.colascione@gmail.com \
--cc=7722@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--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 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.