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 #50 received at 47244 <at> debbugs.gnu.org (full text, mbox):

From: Michael Welsh Duggan <mwd <at> md5i.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: mwd <at> md5i.com, 47244 <at> debbugs.gnu.org, Andreas Schwab <schwab <at> linux-m68k.org>,
 mwd <at> cert.org
Subject: Re: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Thu, 18 Mar 2021 21:50:28 -0400

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Andreas Schwab <schwab <at> linux-m68k.org>
>> Cc: Michael Welsh Duggan <mwd <at> cert.org>,  mwd <at> md5i.com,  47244 <at> 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 <at> md5i.com)
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.