GNU bug report logs - #75056
31.0.50; tty-child-frames with server / multiple clients possible hangs

Previous Next

Package: emacs;

Reported by: Len Trigg <lenbok <at> gmail.com>

Date: Tue, 24 Dec 2024 05:44:02 UTC

Severity: normal

Found in version 31.0.50

Full log


Message #83 received at 75056 <at> debbugs.gnu.org (full text, mbox):

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Len Trigg <lenbok <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 75056 <at> debbugs.gnu.org
Subject: Re: bug#75056: 31.0.50; tty-child-frames with server / multiple
 clients possible hangs
Date: Thu, 23 Jan 2025 20:38:37 +0100
Len Trigg <lenbok <at> gmail.com> writes:

> On Fri, 24 Jan 2025 at 06:34, Gerd Möllmann <gerd.moellmann <at> gmail.com> wrote:
>
>  Eli Zaretskii <eliz <at> gnu.org> writes:
>
>  > What is the value of z_order?
>
>  Len, can you please print
>
>    p root->visible
>
> (gdb) p root->visible
> $1 = 0
> (gdb) p z_order
> $2 = (Lisp_Object) 0x0

Thanks, that explains the crash. I would never had expected that we
try to update invisible frames, hence the assert with --enable-checking
at the start of the function.

Now, the $1000 question is why is mini_frame in redisplay_internal
invisible? Pretty sure it has something to do with multi-tty.

Anyway. I'll develop a fix for that immediate problem tomorrow. I think
I'll just make it not crash for now, and perform the update anyway,
which I guess 30 would do.

Thanks!




This bug report was last modified 110 days ago.

Previous Next


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