unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <acorallo@gnu.org>
Cc: mattias.engdegard@gmail.com, 73914@debbugs.gnu.org,
	monnier@iro.umontreal.ca, mitchell.jkyle@gmail.com
Subject: bug#73914: 30.0.91; abort while reading invalid read syntax from minibuffer
Date: Mon, 21 Oct 2024 13:08:12 +0300	[thread overview]
Message-ID: <86ldyhhipf.fsf@gnu.org> (raw)
In-Reply-To: <yp1fropu9u2.fsf@fencepost.gnu.org> (message from Andrea Corallo on Mon, 21 Oct 2024 04:41:25 -0400)

> From: Andrea Corallo <acorallo@gnu.org>
> Cc: Jonathan Mitchell <mitchell.jkyle@gmail.com>,  Stefan Monnier
>  <monnier@iro.umontreal.ca>,  Mattias Engdegård
>  <mattias.engdegard@gmail.com>,  73914@debbugs.gnu.org
> Date: Mon, 21 Oct 2024 04:41:25 -0400
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Jonathan Mitchell <mitchell.jkyle@gmail.com>
> >> Date: Sun, 20 Oct 2024 14:00:47 -0500
> >> 
> >> Emacs 30.0.91 aborts while reading a lisp integer with invalid read
> >> syntax from the M-: (eval-expression) minibuffer. I can't reproduce this with Emacs 29.4, which correctly shows
> >> an invalid read syntax error message in the minibuffer.
> >> 
> >> [Steps to repoduce]
> >> 1. Do a clean checkout the latest emacs-30 git branch
> >> 2. Build a --with-pgtk and debug build options
> >> 3. Start `emacs -Q' under gdb
> >> 4. Type `M-:' then something with invalid read syntax like `#0400'.
> >
> > Thanks, I installed a fix.
> >
> > Stefan, Andrea, and Mattias: I'd appreciate your comments on the bug
> > and the fix, since this is on the release branch.
> 
> I'm no expert but the fix looks okay to me, also I don't have ATM any
> better strategy in mind other than installing such a fix on the release
> branch.

Thanks for the feedback.





  reply	other threads:[~2024-10-21 10:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-20 19:00 bug#73914: 30.0.91; abort while reading invalid read syntax from minibuffer Jonathan Mitchell
2024-10-20 19:42 ` Eli Zaretskii
2024-10-21  3:04   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-21  5:47     ` Eli Zaretskii
2024-10-21 13:14       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-21  8:41   ` Andrea Corallo
2024-10-21 10:08     ` Eli Zaretskii [this message]
2024-10-21  9:49   ` Mattias Engdegård
2024-10-21 10:07     ` Eli Zaretskii

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=86ldyhhipf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73914@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=mattias.engdegard@gmail.com \
    --cc=mitchell.jkyle@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).