GNU bug report logs - #47244
28.0.50; SIGSEGV in long-runnning Emacs

Previous Next

Package: emacs;

Reported by: Michael Welsh Duggan <md5i <at> md5i.com>

Date: Thu, 18 Mar 2021 15:40:01 UTC

Severity: normal

Found in version 28.0.50

Done: Michael Welsh Duggan <mwd <at> md5i.com>

Bug is archived. No further changes may be made.

Full log


Message #107 received at 47244 <at> debbugs.gnu.org (full text, mbox):

From: Michael Welsh Duggan <mwd <at> cert.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: "mwd <at> md5i.com" <mwd <at> md5i.com>,
 "47244 <at> debbugs.gnu.org" <47244 <at> debbugs.gnu.org>, Eli Zaretskii <eliz <at> gnu.org>,
 "schwab <at> linux-m68k.org" <schwab <at> linux-m68k.org>
Subject: Re: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Tue, 23 Mar 2021 11:53:52 -0400
martin rudalics <rudalics <at> gmx.at> writes:

>  >>    break buffer.c:1840 if redisplaying_p != 0 && b->window_count > 0
>  >
>  > This triggered today.
>
> Could you try running Emacs inserting before the last two lines of
> `switch-to-prev-buffer'
>
>      ;; Return new-buffer.
>      new-buffer))
>
> a check so this stretch appears as
>
>      (when (and (eq bury-or-kill 'kill) (eq new-buffer old-buffer))
>        (error "Could not replace buffer %s in window %s"
>               old-buffer window))
>
>      ;; Return new-buffer.
>      new-buffer))
>
> If `replace-buffer-in-windows' is the culprit, this should trigger the
> bug sooner.
>
> Thanks, martin

Okay.  Running with this.  I still have the other emacs that segfaulted
in gdb if you want/need anything else from it.

-- 
Michael Welsh Duggan
(mwd <at> cert.org)




This bug report was last modified 4 years and 28 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.