From: Toon Claes <toon@tonotdo.com>
To: <10652@debbugs.gnu.org>
Subject: bug#10652: font-lock very slow for C++
Date: Wed, 14 Mar 2012 11:45:14 +0200 [thread overview]
Message-ID: <c85c535bd39ff7fcbc80a8b39a2ccf2b@tonotdo.com> (raw)
In-Reply-To: <m2vcntbfvb.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
I'm also having trouble with some cpp files.
I've got one file
(572 lines, 18560 bytes), that always causes emacs 24 to hang. Emacs
23.3.1 handles this file just fine.
I am using emacs from git:
commit 6ba3ea4d2625fac8b5fb839f11eeb074d699687e
Author: Christopher
Schmidt <christopher@ch.ristopher.com>
Date: Mon Mar 12 01:31:44 2012
+0800
* ibuffer.el (ibuffer-redisplay): Remove gratuitous error.
When GDB was hanging I stopped the process with GDB, with this
backtrace:
http://pastebin.com/ssB96ue4
I'm not familiar with the
emacs source code, but I do not know this is normal.
If I can help
investigation the problem more in detail, let me know.
Unfortunately I
am not allowed to share the source file with you.
Also I've tried to
decrease font-lock-maximum-decoration to 1, but this didn't have effect.
[-- Attachment #2: Type: text/html, Size: 1117 bytes --]
next prev parent reply other threads:[~2012-03-14 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 11:15 bug#10652: 24.0.93; font-lock very slow for C++ Helmut Eller
2012-02-26 9:47 ` Chong Yidong
2012-03-01 19:36 ` Alan Mackenzie
2012-03-02 22:27 ` Alan Mackenzie
2012-03-16 14:19 ` Alan Mackenzie
2012-03-14 9:45 ` Toon Claes [this message]
2012-03-16 10:18 ` bug#10652: Recursive loop in alloc.c [ Was: font-lock very slow for C++ ] Alan Mackenzie
[not found] ` <20120316101838.GB3439@acm.acm>
2012-03-16 10:34 ` Andreas Schwab
2012-03-16 14:24 ` bug#10652: 24.0.93; font-lock very slow for C++ Alan Mackenzie
2012-03-28 7:07 ` bug#10652: " Toon Claes
2012-03-29 9:35 ` Alan Mackenzie
2012-03-29 19:46 ` Toon Claes
2012-03-29 22:00 ` Alan Mackenzie
2012-04-02 7:48 ` Toon Claes
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=c85c535bd39ff7fcbc80a8b39a2ccf2b@tonotdo.com \
--to=toon@tonotdo.com \
--cc=10652@debbugs.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).