From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 41239@debbugs.gnu.org
Subject: bug#41239: GTK builds crashing in XTread_socket after deleting a frame
Date: Wed, 13 May 2020 21:04:28 +0300 [thread overview]
Message-ID: <83v9kz679v.fsf@gnu.org> (raw)
In-Reply-To: <b0e04656-3471-f4d9-8ccd-049aa3167332@gmx.at> (message from martin rudalics on Wed, 13 May 2020 19:42:43 +0200)
> From: martin rudalics <rudalics@gmx.at>
> Date: Wed, 13 May 2020 19:42:43 +0200
>
> This looks like yet another GTK specific crash where we apparently can't
> do much. But maybe someone can spot a pattern we could employ to avoid
> the XTread_socket calls when deleting a frame.
Isn't block_input inside Fdelete_frame what you want?
However, the first backtrace doesn't show Fdelete_frame in the
backtrace, so I'm not sure what's going on there.
next prev parent reply other threads:[~2020-05-13 18:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 17:42 bug#41239: GTK builds crashing in XTread_socket after deleting a frame martin rudalics
2020-05-13 18:04 ` Eli Zaretskii [this message]
2020-05-14 7:54 ` martin rudalics
2020-05-14 14:22 ` Eli Zaretskii
2020-05-15 18:07 ` martin rudalics
2020-05-15 18:58 ` Eli Zaretskii
2020-05-16 8:45 ` martin rudalics
2020-05-20 1:50 ` Noam Postavsky
2020-05-20 9:06 ` martin rudalics
2020-05-20 16:07 ` Eli Zaretskii
2020-05-22 1:23 ` Noam Postavsky
2020-05-22 9:31 ` martin rudalics
2020-05-22 11:05 ` Eli Zaretskii
2020-05-22 11:25 ` Noam Postavsky
2020-05-22 12:08 ` Eli Zaretskii
2020-05-22 12:22 ` Noam Postavsky
2020-05-22 12:37 ` Eli Zaretskii
2020-05-25 0:31 ` Noam Postavsky
2020-09-27 14:43 ` Lars Ingebrigtsen
2020-05-22 13:03 ` martin rudalics
[not found] ` <87d06vl5le.fsf@gmail.com>
[not found] ` <83r1vb189z.fsf@gnu.org>
2020-05-23 12:08 ` Noam Postavsky
2020-05-23 12:38 ` martin rudalics
2020-05-25 0:11 ` Noam Postavsky
2020-05-26 8:03 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v9kz679v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=41239@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.