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

Previous Next

Full log

View this message in rfc822 format

From: martin rudalics <rudalics <at> gmx.at>
To: Michael Welsh Duggan <mwd <at> cert.org>
Cc: Michael Welsh Duggan <mwd <at> md5i.com>, "47244 <at> debbugs.gnu.org" <47244 <at> debbugs.gnu.org>, "schwab <at> linux-m68k.org" <schwab <at> linux-m68k.org>
Subject: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Tue, 6 Apr 2021 19:00:37 +0200

>> The mysterious aspect is (2): Why did window_list skip the *Server*
>> window?
>
> Good question.  I plan to set Vwindow_list to nil and call it to see
> what happens.

This should resolve the mystery.

>> What is the value of FRAME_ROOT_WINDOW (f) where f is the
>> *Server* frame?  What is the name of that window's buffer?
>
> It's a window containing the buffer "*Server*".

So a bad FRAME_ROOT_WINDOW can't be the cause for (2).

>> IIUC the *Server* frame does not have a minibuffer window - correct?
>
> It didn't appear in Vwindow_list, but it does have a minibuffer.
>
> (gdb) p $116->minibuffer_window
> $139 = XIL(0x555556fc8185)
> (gdb) xwindow
> $140 = (struct window *) 0x555556fc8180
> 84x1+0+59
> (gdb) p $140->contents
> $141 = XIL(0x7ffff2a3cb15)
> (gdb) xbuffer
> $142 = (struct buffer *) 0x7ffff2a3cb10
> 0x7ffff2d244ea " *Minibuf-0*"
>
> I will note that the window itself is different than the one on the
> Vwindow_list with the same contents.

Are you sure it's on the same frame as the *Server* window (w->frame
gives you that)?  What is the value of w->next for the *Server* window?

martin

Previous Next

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