From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: "Chris Hecker" <checker@d6.com>
Cc: 59038@debbugs.gnu.org, Alan Mackenzie <acm@muc.de>
Subject: bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely
Date: Sat, 05 Nov 2022 06:12:37 +0100 [thread overview]
Message-ID: <m235ayx9ve.fsf@Mini.fritz.box> (raw)
In-Reply-To: <em9149954c-deeb-4542-a0b0-bca0884d2512@checker-blade15> (Chris Hecker's message of "Sat, 05 Nov 2022 02:48:42 +0000")
"Chris Hecker" <checker@d6.com> writes:
> gunzip this file (it's a c header file base64 encoded from
> googlesource.com) to Looper.h and load it with 28.2 emacs -Q and it'll
> infinite loop pegging one core.
Thanks for the report, Chris.
This is reproducible with master fd3f51b7c3a6649ee3db12d33b056b1afdbfa7e9.
It might be related to cc-mode, so I've CC'd Alan. Emacs goes into an
infloop while font-locking the encoded .h file. Below are some Lisp
backtraces from interrupting the loop:
(unsigned char *) data = 0x0000000100280ecb "skip-syntax-backward"
(unsigned char *) data = 0x000000010328e580 "c-beginning-of-current-token"
(unsigned char *) data = 0x000000010328f9e0 "c-update-brace-stack"
(unsigned char *) data = 0x000000010328fb40 "c-brace-stack-at"
(unsigned char *) data = 0x000000010328fb60 "c-bs-at-toplevel-p"
(unsigned char *) data = 0x000000010328fcd0 "c-find-decl-spots"
(unsigned char *) data = 0x00000001032c96d8 "c-font-lock-declarations"
(unsigned char *) data = 0x0000000104b79b52 "font-lock-fontify-keywords-region"
(unsigned char *) data = 0x0000000104b7f7d5 "font-lock-default-fontify-region"
(unsigned char *) data = 0x00000001032fc2f8 "c-font-lock-fontify-region"
(unsigned char *) data = 0x0000000104bcf23f "font-lock-fontify-region"
PVEC_COMPILED
(unsigned char *) data = 0x000000010027b168 "run-hook-wrapped"
(unsigned char *) data = 0x0000000104b6b2f2 "jit-lock--run-functions"
(unsigned char *) data = 0x0000000104b9887d "jit-lock-fontify-now"
(unsigned char *) data = 0x0000000104bb05ff "jit-lock-function"
(unsigned char *) data = 0x000000010027f89f "redisplay_internal (C function)"
(unsigned char *) data = 0x0000000100280f1c "parse-partial-sexp"
(unsigned char *) data = 0x000000010328f640 "c-syntactic-re-search-forward"
(unsigned char *) data = 0x000000010328f9e0 "c-update-brace-stack"
(unsigned char *) data = 0x000000010328fb40 "c-brace-stack-at"
(unsigned char *) data = 0x000000010328fb60 "c-bs-at-toplevel-p"
(unsigned char *) data = 0x000000010328fcd0 "c-find-decl-spots"
(unsigned char *) data = 0x00000001032c96d8 "c-font-lock-declarations"
(unsigned char *) data = 0x0000000104b79b52 "font-lock-fontify-keywords-region"
(unsigned char *) data = 0x0000000104b7f7d5 "font-lock-default-fontify-region"
(unsigned char *) data = 0x00000001032fc2f8 "c-font-lock-fontify-region"
(unsigned char *) data = 0x0000000104bcf23f "font-lock-fontify-region"
PVEC_COMPILED
(unsigned char *) data = 0x000000010027b168 "run-hook-wrapped"
(unsigned char *) data = 0x0000000104b6b2f2 "jit-lock--run-functions"
(unsigned char *) data = 0x0000000104b9887d "jit-lock-fontify-now"
(unsigned char *) data = 0x0000000104bb05ff "jit-lock-function"
(unsigned char *) data = 0x000000010027f89f "redisplay_internal (C function)"
(unsigned char *) data = 0x00000001002783c1 "re-search-forward"
(unsigned char *) data = 0x000000010328f640 "c-syntactic-re-search-forward"
(unsigned char *) data = 0x000000010328f9e0 "c-update-brace-stack"
(unsigned char *) data = 0x000000010328fb40 "c-brace-stack-at"
(unsigned char *) data = 0x000000010328fb60 "c-bs-at-toplevel-p"
(unsigned char *) data = 0x000000010328fcd0 "c-find-decl-spots"
(unsigned char *) data = 0x00000001032c96d8 "c-font-lock-declarations"
(unsigned char *) data = 0x0000000104b79b52 "font-lock-fontify-keywords-region"
(unsigned char *) data = 0x0000000104b7f7d5 "font-lock-default-fontify-region"
(unsigned char *) data = 0x00000001032fc2f8 "c-font-lock-fontify-region"
(unsigned char *) data = 0x0000000104bcf23f "font-lock-fontify-region"
PVEC_COMPILED
(unsigned char *) data = 0x000000010027b168 "run-hook-wrapped"
(unsigned char *) data = 0x0000000104b6b2f2 "jit-lock--run-functions"
(unsigned char *) data = 0x0000000104b9887d "jit-lock-fontify-now"
(unsigned char *) data = 0x0000000104bb05ff "jit-lock-function"
(unsigned char *) data = 0x000000010027f89f "redisplay_internal (C function)"
next prev parent reply other threads:[~2022-11-05 5:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 2:48 bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely Chris Hecker
2022-11-05 5:12 ` Gerd Möllmann [this message]
2022-11-05 7:01 ` Eli Zaretskii
2022-11-05 7:50 ` Gerd Möllmann
2022-11-05 8:21 ` Chris Hecker
2022-11-05 8:45 ` Gerd Möllmann
2022-11-05 9:30 ` Eli Zaretskii
2022-11-05 10:39 ` bug#59038: Re[2]: " Chris Hecker
2022-11-05 11:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-05 15:01 ` Chris Hecker
2022-11-06 5:17 ` Gerd Möllmann
2022-11-05 22:03 ` Alan Mackenzie
2022-11-06 6:00 ` Eli Zaretskii
2022-11-05 9:28 ` Eli Zaretskii
2022-11-06 5:18 ` Gerd Möllmann
2022-11-05 22:27 ` Gregory Heytings
2022-11-05 23:41 ` Gregory Heytings
2022-11-06 3:58 ` Phil Sainty
2022-11-06 5:20 ` Gerd Möllmann
2022-11-06 13:54 ` Alan Mackenzie
2022-11-06 9:18 ` Gregory Heytings
2022-11-06 13:52 ` Eli Zaretskii
2022-11-06 16:34 ` Alan Mackenzie
2022-11-07 7:55 ` Gerd Möllmann
[not found] ` <Y2fiMTlfuNqae7zp@acm>
2022-11-06 19:46 ` bug#59038: Re[2]: " Chris Hecker
2022-11-07 12:25 ` Alan Mackenzie
2022-11-05 6:52 ` Eli Zaretskii
2022-11-05 10:45 ` Phil Sainty
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=m235ayx9ve.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=59038@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=checker@d6.com \
/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).