bug#44502:

[Alan Mackenzie <acm@muc.de>]

Hello, Eli.

On Fri, Aug 12, 2022 at 09:27:21 +0300, Eli Zaretskii wrote:
> > From: andrei.elkin@pp.inet.fi
> > Cc: 44502@debbugs.gnu.org
> > Date: Thu, 11 Aug 2022 22:10:12 +0300

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

> > >> From: andrei.elkin@pp.inet.fi
> > >> Cc: 44502@debbugs.gnu.org
> > >> Date: Thu, 11 Aug 2022 21:19:06 +0300

> > >> (gdb) p window
> > >> $4 = XIL(0x55555b038855)
> > >> (gdb) xwindow
> > >> $5 = (struct window *) 0x55555b038850
> > >> 124x1+0+80
> > >> (gdb) print XWINDOW(window)->contents
> > >> $6 = XIL(0x7fffea1bd07d)
> > >> (gdb) xbuffer
> > >> $7 = (struct buffer *) 0x7fffea1bd078
> > >> 0x7fffea4aedc1 " *Minibuf-0*"
> > >> (gdb) print selected_window
> > >> $8 = XIL(0x55555b038645)
> > >> (gdb) xwindow
> > >> $9 = (struct window *) 0x55555b038640
> > >> 124x80+0+0
> > >> (gdb) print XWINDOW(selected_window)->contents
> > >> $10 = XIL(0x5555577f9475)
> > >> (gdb) xbuffer
> > >> $11 = (struct buffer *) 0x5555577f9470
> > >> 0x555559788ff0 "magit: A<10.6>"

> > > Do you remember what were you doing when this assertion violation
> > > happened?

> > Something like

> >   C-u M-x shell



> > > Also, are you using a separate minibuffer frame?

> > No

> Then I tend to think that the assertion there is simply wrong.

> Adding Alan to CC, since this seems to be related to the
> minibuffer-follows-selected-frame feature.  Alan, this happens in
> Emacs 28, so trying to fix it on the release branch in a safe way is
> important.  TIA.

OK, I'll have a look at it over the weekend.

-- 
Alan Mackenzie (Nuremberg, Germany).