From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lenbok@gmail.com, 75056@debbugs.gnu.org
Subject: bug#75056: 31.0.50; tty-child-frames with server / multiple clients possible hangs
Date: Fri, 27 Dec 2024 16:56:03 +0100 [thread overview]
Message-ID: <m2y10186i4.fsf@gmail.com> (raw)
In-Reply-To: <86ldw1w51g.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 27 Dec 2024 16:53:47 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: lenbok@gmail.com, 75056@debbugs.gnu.org
>> Date: Fri, 27 Dec 2024 14:17:11 +0100
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > But I'm not yet sure this is what we see in this case, which is why I
>> > asked for a C backtrace. Producing it should be easy: just reproduce
>> > the problem, then attach a debugger and produce the backtrace.
>>
>> See below. AFAICS, Emacs is waiting for input, and when we have some,
>> the wrong things will happen. Please note that this is not a full debug
>> build.
>
> Thanks. This lacks the equivalent of "xbacktrace", so a bit hard to
> interpret, but I see read-from-minibuffer which called recursive-edit.
>
> What is the recipe for this, starting from "emacs -Q", please?
The one the OP gave is good.
> Can this be reproduced without posframe?
No idea.
next prev parent reply other threads:[~2024-12-27 15:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 5:43 bug#75056: 31.0.50; tty-child-frames with server / multiple clients possible hangs Len Trigg
2024-12-25 11:54 ` Eli Zaretskii
2024-12-25 11:59 ` Gerd Möllmann
2024-12-27 6:04 ` Gerd Möllmann
2024-12-27 8:18 ` Eli Zaretskii
2024-12-27 8:46 ` Gerd Möllmann
2024-12-27 8:54 ` Eli Zaretskii
2024-12-27 9:04 ` Gerd Möllmann
2024-12-27 12:28 ` Eli Zaretskii
2024-12-27 12:47 ` Gerd Möllmann
2024-12-27 13:02 ` Eli Zaretskii
2024-12-27 13:17 ` Gerd Möllmann
2024-12-27 14:53 ` Eli Zaretskii
2024-12-27 15:56 ` Gerd Möllmann [this message]
2024-12-27 18:13 ` Len Trigg
2024-12-27 18:23 ` Len Trigg
2024-12-28 7:52 ` Eli Zaretskii
2024-12-28 19:55 ` Len Trigg
2025-01-05 16:41 ` Eli Zaretskii
2025-01-07 18:04 ` Len Trigg
[not found] ` <CAOGVwenNt8a0HmSXTnqu5_FKkxEVMDw0hmak-MLk7Sn6up_wtg@mail.gmail.com>
2024-12-28 7:44 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2y10186i4.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=75056@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lenbok@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).