all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: 48337@debbugs.gnu.org
Subject: bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related)
Date: Sat, 15 May 2021 12:00:01 +0000	[thread overview]
Message-ID: <YJ+3wRCADgrlGD1x@ACM> (raw)
In-Reply-To: <87o8ddc59q.fsf@linaro.org>

Hello, Alex.

On Fri, May 14, 2021 at 23:35:34 +0100, Alex Bennée wrote:

> Alan Mackenzie <acm@muc.de> writes:

> > On Fri, May 14, 2021 at 17:52:46 +0100, Alex Bennée wrote:
> >> Sadly not, testing with 780b1db126fcfdbb50da5c1acf24b3c6e614dd9f I got a
> >> crash when I tried to switch buffer.

> > Thanks for the two dumps.  They make it obvious what has happened.
> > buffer-list-update-hook is getting called before the new minibuffer has
> > been pushed onto the minnibuffer list.

> > Could I ask you to try out the following patch which should fix that
> > problem.  Thanks!

> That seems to sort out both the recent crash and the original failure
> mode I reported in this bug.

Excellent!  Thanks for doing the testing.

I think I'd rather leave the bug open a bit longer, just in case any
other failures turn up.


> > diff --git a/src/minibuf.c b/src/minibuf.c
> > index 428998a639..d4702ee684 100644
> > --- a/src/minibuf.c
> > +++ b/src/minibuf.c
> > @@ -653,11 +653,11 @@ read_minibuf (Lisp_Object map, Lisp_Object initial, Lisp_Object prompt,
> >        return unbind_to (count, val);
> >      }

> > -  minibuf_level++;         /* Before calling choose_minibuf_frame.  */
> >    /* Ensure now that the latest minibuffer has been created, in case
> >       anything happens which depends on MINNIBUF_LEVEL and
> >       Vminibuffer_list being consistent with eachother.  */
> > -  minibuffer = get_minibuffer (minibuf_level);
> > +  minibuffer = get_minibuffer (minibuf_level + 1);
> > +  minibuf_level++;		/* Before calling choose_minibuf_frame.  */
> >
> >    /* Choose the minibuffer window and frame, and take action on them.  */

> -- 
> Alex Bennée

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2021-05-15 12:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87tunasd2u.fsf@linaro.org>
2021-05-10 19:30 ` bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related) Alex Bennée
2021-05-10 19:34   ` bug#48337: Alex Bennée
2021-05-11  2:24   ` bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related) Eli Zaretskii
2021-05-11  6:51     ` Alex Bennée
2021-05-11  8:23       ` Alex Bennée
2021-05-11  8:54         ` Alex Bennée
2021-05-11 12:21       ` Eli Zaretskii
2021-05-11 12:54         ` Alex Bennée
2021-05-11 13:42           ` Eli Zaretskii
2021-05-11 13:47             ` Eli Zaretskii
2021-05-11 19:45             ` Alan Mackenzie
2021-05-11 19:55               ` Eli Zaretskii
2021-05-12 18:54                 ` Alan Mackenzie
2021-05-13  7:54                   ` martin rudalics
2021-05-13  9:52                     ` Alan Mackenzie
2021-05-13 11:54                       ` Alan Mackenzie
2021-05-13 12:09                         ` Alan Mackenzie
2021-05-14 15:20                     ` Gregory Heytings
2021-05-14 16:05                       ` Eli Zaretskii
2021-05-14 17:31                         ` Gregory Heytings
2021-05-14 18:19                           ` Eli Zaretskii
2021-05-15  9:45                             ` Gregory Heytings
2021-05-11 20:14       ` Alan Mackenzie
2021-05-11 22:07         ` Alex Bennée
2021-05-14 16:31           ` Alan Mackenzie
2021-05-14 16:52             ` Alex Bennée
2021-05-14 18:40               ` Alan Mackenzie
2021-05-14 22:35                 ` Alex Bennée
2021-05-15 12:00                   ` Alan Mackenzie [this message]
2021-05-16 14:24                     ` Alan Mackenzie

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=YJ+3wRCADgrlGD1x@ACM \
    --to=acm@muc.de \
    --cc=48337@debbugs.gnu.org \
    --cc=alex.bennee@linaro.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.