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, acm@muc.de
Subject: bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related)
Date: Fri, 14 May 2021 16:31:56 +0000	[thread overview]
Message-ID: <YJ6l/KObBu3BvBFV@ACM> (raw)
In-Reply-To: <87y2ckgby0.fsf@linaro.org>

Hello, Alex.

On Tue, May 11, 2021 at 23:07:01 +0100, Alex Bennée wrote:

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

> > On Tue, May 11, 2021 at 07:51:20 +0100, Alex Bennée wrote:
> >> I can now recreate at will with a magit sequence (l o hackbox/ TAB) which
> >> triggers a minibuffer re-size to accommodate the list of git branches:

> > Could you possibly give us a precise recipe to reproduce this bug, and a
> > GDB backtrace with Emacs compiled with CFLAGS='-O0 g3' (or similar)?  So
> > much of the needed information in your large dump post has been
> > optimised away by the compiler.  Would you please also make sure that
> > the Lisp backtrace is at the end of the GDB backtrace.  I think this
> > should happen automatically if you have an Emacs .gdbinit in the
> > directory where you start GDB from.

I now understand what the bug was, and have just committed a patch which
should have fixed it.  Could you please update your Emacs and test your
bug scenario, and either confirm to me that the bug is fixed, or say what
is still wrong.  If this has to wait until Monday that's OK, but please
let us know that.

Then, hopefully, we can close the bug.

> The later rr dumps have more symbols but didn't have the benefit of the
> Emacs' .gdbinit Lips backtrace. However I'm fairly confident it's being
> triggered by doom-modeline:

The actual trigger was something on buffer-list-update-hook.  That should
now no longer cause a problem.

[ .... ]

> -- 
> Alex Bennée

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2021-05-14 16:31 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 [this message]
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
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=YJ6l/KObBu3BvBFV@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.