From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 59038@debbugs.gnu.org, acm@muc.de, checker@d6.com
Subject: bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely
Date: Sat, 05 Nov 2022 11:28:10 +0200 [thread overview]
Message-ID: <83bkpl4uol.fsf@gnu.org> (raw)
In-Reply-To: <9719cff6-4534-46d9-0fed-1476633ac37d@gmail.com> (message from Gerd Möllmann on Sat, 5 Nov 2022 08:50:33 +0100)
> Date: Sat, 5 Nov 2022 08:50:33 +0100
> Cc: checker@d6.com, 59038@debbugs.gnu.org, acm@muc.de
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>
> On 05.11.22 08:01, Eli Zaretskii wrote:
> > What is reproducible, exactly?
>
> I don't understand. The infinite loop is reproducible, "pegging one
> core" as he expressed it, using up one CPU core.
Not here, it isn't.
> > Visiting the file is almost
> > instantaneous here, in Emacs 29. What did you do to get Emacs into an
> > infloop?
>
> Maybe I switched applications with Cmd-TAB, or something else triggering
> redisplay. Do a M-x or C-l.
No, that doesn't trigger it. Only M-> does.
> > It is IMO unreasonable to expect CC Mode to do something sensible with
> > random sequence of characters that don't resemble C in any way.
>
> I think no-one expects that. The bug is the uninterruptable loop or
> whatever causes it.
It's nice to have that fixed, if it isn't too complex, but in general
visiting such a file as C file is not a reasonable thing to do.
next prev parent reply other threads:[~2022-11-05 9:28 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
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 [this message]
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=83bkpl4uol.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59038@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=checker@d6.com \
--cc=gerd.moellmann@gmail.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).