From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 10792@debbugs.gnu.org, john@yates-sheets.org
Subject: bug#10792: 24.0.93; emacs goes comatose opening C header
Date: Sat, 11 Feb 2012 22:17:55 +0200 [thread overview]
Message-ID: <83k43tyvik.fsf@gnu.org> (raw)
In-Reply-To: <20120211200507.GB3969@acm.acm>
> Date: Sat, 11 Feb 2012 20:05:07 +0000
> From: Alan Mackenzie <acm@muc.de>
> Cc: 10792@debbugs.gnu.org
>
> On Sat, Feb 11, 2012 at 12:26:36PM -0500, John Yates wrote:
> > When I attemt to visit the following header emacs locks up. If
> > I make the contents of the macro significantly shorted emacs is
> > able to open and fontlock it successfully. To me this suggests
> > some form of n-squared processing.
>
> For once, this problem has nothing to do with font locking.
It doesn't? If I attach GDB to Emacs, I get this Lisp backtrace:
Lisp Backtrace:
"c-end-of-macro" (0x827d74)
"c-syntactic-end-of-macro" (0x827fc4)
"c-state-safe-place" (0x828224)
"c-literal-limits" (0x828484)
"c-set-fl-decl-start" (0x8286d4)
"c-context-set-fl-decl-start" (0x828924)
0x3422320 PVEC_COMPILED
"mapc" (0x828d04)
"c-font-lock-fontify-region" (0x828f54) <<<<<<<<<<<<<<<<<<<<<
"font-lock-fontify-region" (0x8292d8) <<<<<<<<<<<<<<<<<<<<<
"run-hook-with-args" (0x8292d4)
"byte-code" (0x8294a0)
"jit-lock-fontify-now" (0x829894) <<<<<<<<<<<<<<<<<<<<<
"jit-lock-function" (0x829c24) <<<<<<<<<<<<<<<<<<<<<
"recenter" (0x82f6b4)
"end-of-buffer" (0x82f954)
"call-interactively" (0x82fb84)
> It happens when the buffer length exceeds 3000 bytes. :-)
You mean, the macro definition length, right?
next prev parent reply other threads:[~2012-02-11 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 17:26 bug#10792: 24.0.93; emacs goes comatose opening C header John Yates
2012-02-11 19:55 ` Eli Zaretskii
2012-02-11 20:14 ` Andreas Schwab
2012-02-11 20:05 ` Alan Mackenzie
2012-02-11 20:17 ` Eli Zaretskii [this message]
2012-02-11 20:22 ` Alan Mackenzie
2012-02-11 20:38 ` Eli Zaretskii
2012-02-11 21:53 ` Alan Mackenzie
2012-02-11 22:39 ` Alan Mackenzie
2012-02-12 0:28 ` John Yates
2012-02-12 0:53 ` John Yates
2012-02-14 5:45 ` 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=83k43tyvik.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10792@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=john@yates-sheets.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.