bug#73914: 30.0.91; abort while reading invalid read syntax from minibuffer

[Eli Zaretskii <eliz@gnu.org>]

> Cc: mattias.engdegard@gmail.com, 73914@debbugs.gnu.org,
>  monnier@iro.umontreal.ca, mitchell.jkyle@gmail.com
> Date: Mon, 21 Oct 2024 13:08:12 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > 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.

No further comments, so I'm now closing this bug.