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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: mwd <at> md5i.com, 47244 <at> debbugs.gnu.org, schwab <at> linux-m68k.org, mwd <at> cert.org
Subject: Re: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Mon, 29 Mar 2021 18:21:47 +0300

> Date: Mon, 29 Mar 2021 18:07:18 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: mwd <at> md5i.com, schwab <at> linux-m68k.org, 47244 <at> debbugs.gnu.org
> 
> Actually, no, I don't think it can be with-current-buffer, it must be
> something else.  I wonder how we ended up being at top-level with
> current buffer being " *nntpd*" and the selected window's buffer being
> something else, which was killed?  Hmm...

Martin, could it be that replace-buffer-in-windows fails to replace a
buffer?  Suppose kill-buffer is called to kill a buffer that is shown
in the selected window, but replace-buffer-in-windows fails to replace
it -- can that happen?

And another question: can a window be selected if its buffer is dead?
Or is it possible to set a dead buffer as a window's buffer?

Previous Next

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