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 #173 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: Mon, 29 Mar 2021 12:26:47 -0400
martin rudalics <rudalics <at> gmx.at> writes:

>  > 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?
>
> That's what we tried earlier with the check in `switch-to-prev-buffer'.
> Michael did you run with that check this time or did you remove it?  If
> the latter, please reinsert it for the next time.  But let's recall that
> at the time of the last segfault that particular check did not trigger.

I had removed it, sorry.  I'll put it in for the next time.

>  > 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?
>
>  From what we can say now one of these must have happened.  The dead
> buffer comes from the selected window.  It does not come from the
> attempt to restore the current buffer from a temporarily saved one.
>
> One thing I'm not even sure about is whether the selected window is
> still "live" when were trying to make its buffer current.  Michael is
> this "window" supposed to be the only one on its frame?  Are we sure
> that it is not the minibuffer window?  In either case we could try to
> investigate its parent and geometry: What do

I think so.  Both the *Server* window and the *Group* window will, under
normal circumstances, be the only window on the frame.

> p XWINDOW (selected_window)->parent
> p XWINDOW (selected_window)->prev
> p XWINDOW (selected_window)->next
> p XWINDOW (selected_window)->top_line
> p XWINDOW (selected_window)->pixel_height
>
> print?

(gdb) p XWINDOW (selected_window)->parent
$15 = XIL(0)
(gdb) p XWINDOW (selected_window)->prev
$16 = XIL(0)
(gdb) p XWINDOW (selected_window)->next
$17 = XIL(0x555556e96635)
(gdb) p XWINDOW (selected_window)->top_line
$18 = 0
(gdb) p XWINDOW (selected_window)->pixel_height
$19 = 995

-- 
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.