bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs

[Michael Welsh Duggan]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andreas Schwab <schwab@linux-m68k.org>
>> Cc: Michael Welsh Duggan <mwd@cert.org>,  mwd@md5i.com,  
>> 47244@debbugs.gnu.org
>> Date: Thu, 18 Mar 2021 21:13:40 +0100
>> 
>> > So the selected window's buffer was killed.  How is that possible?
>> 
>> Perhaps during run_window_change_functions.
>
> Something like that, yes.  But I don't understand how that can happen
> technically: kill-buffer selects another buffer when killing the
> current one.  So how was that buffer killed, and yet stayed current?

Hmm...  Is there a set of printfs we could add that would provide useful
information for the next time I trigger the crash?

-- 
Michael Welsh Duggan
(md5i@md5i.com)