From: martin rudalics <rudalics@gmx.at>
To: Noam Postavsky <npostavs@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 41239@debbugs.gnu.org
Subject: bug#41239: GTK builds crashing in XTread_socket after deleting a frame
Date: Sat, 23 May 2020 14:38:03 +0200 [thread overview]
Message-ID: <4da5c7c1-ab32-96ee-ef2b-d7c88c8a40cc@gmx.at> (raw)
In-Reply-To: <87a71yluph.fsf@gmail.com>
> Not really no, but I have what might be a clue. I can trigger this
> condition much more reliably (about 3 in 4, instead of 1 in 10; perhaps
> 1 in 10 times I was doing the following thing by accident), by
> intentionally moving the mouse over another popup location without
> letting it pop up, before doing the 'wait for popup and kill frame'
> procedure.
Does not seem to help here.
> So maybe our cleanup is too thorough in the case where we
> call xg_prepare_tooltip but the tooltip ends up not being shown.
One observation I've made is that with emacs -Q and switching between
two frames I can occasionally pop up an Emacs tooltip which means that
preparing the GTK tooltip failed for whatever reason.
>> How did you do that? Did you build GTK with debugging information?
>
> No, just 'break g_log' in gdb works.
What did you install for that to work? Would
https://wiki.gnome.org/Newcomers/DebianSourceDebugging
cover it?
martin
next prev parent reply other threads:[~2020-05-23 12:38 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
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 [this message]
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
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=4da5c7c1-ab32-96ee-ef2b-d7c88c8a40cc@gmx.at \
--to=rudalics@gmx.at \
--cc=41239@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@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).