From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 42655@debbugs.gnu.org, eggert@cs.ucla.edu, uyennhi.qm@gmail.com,
bhavin7392@gmail.com, monnier@iro.umontreal.ca
Subject: bug#42655: 27.1; iconify-frame on a Lucid build may stuck the frame
Date: Thu, 06 Aug 2020 16:47:00 +0300 [thread overview]
Message-ID: <83k0yb999n.fsf@gnu.org> (raw)
In-Reply-To: <871rkki44t.fsf@gmail.com> (message from Tino Calancha on Thu, 06 Aug 2020 10:13:06 +0200)
> From: Tino Calancha <tino.calancha@gmail.com>
> Cc: Bhavin Gandhi <bhavin7392@gmail.com>, 42655@debbugs.gnu.org,
> eggert@cs.ucla.edu, uyennhi.qm@gmail.com, monnier@iro.umontreal.ca
> Date: Thu, 06 Aug 2020 10:13:06 +0200
>
> > (gdb) p *$2->output_data.x
> >
> > This assumes that $2 is as you have show previously, i.e. a pointer to struct frame that corresponds to the selected frame.
>
> (gdb) xframe (selected_frame)
> $3 = (struct frame *) 0x234f888
> "emacs@localhost.example.com"
> (gdb) p *$3->output_data.x
> $4 = {
Thanks. Looks like we never get the MapNotify event from X windows?
Can you verify that, either by running the xev utility or by setting a
breakpoint in xterm.c:handle_one_xevent when MapNotify is handled, and
repeating the recipe?
next prev parent reply other threads:[~2020-08-06 13:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 18:46 bug#42655: 27.1; iconify-frame on a Lucid build may stuck the frame Tino Calancha
2020-08-01 18:53 ` Eli Zaretskii
2020-08-02 13:07 ` Tino Calancha
2020-08-02 14:34 ` Eli Zaretskii
2020-08-03 19:46 ` Tino Calancha
2020-08-03 21:29 ` Stefan Monnier
2020-08-04 2:21 ` Eli Zaretskii
2020-08-04 3:59 ` Eli Zaretskii
2020-08-04 14:20 ` Eli Zaretskii
2020-08-04 15:14 ` Bhavin Gandhi
2020-08-04 16:40 ` Eli Zaretskii
2020-08-04 18:53 ` Bhavin Gandhi
2020-08-04 19:07 ` Eli Zaretskii
2020-08-05 17:23 ` Bhavin Gandhi
2020-08-05 18:43 ` Eli Zaretskii
2020-08-05 18:57 ` Tino Calancha
2020-08-06 2:29 ` Eli Zaretskii
2020-08-06 5:41 ` Bhavin Gandhi
2020-08-06 7:43 ` Eli Zaretskii
2020-08-06 8:13 ` Tino Calancha
2020-08-06 13:47 ` Eli Zaretskii [this message]
2020-08-06 13:57 ` Eli Zaretskii
2020-08-06 14:18 ` Tino Calancha
2020-08-06 14:37 ` Tino Calancha
2020-08-07 5:53 ` Eli Zaretskii
2020-08-07 11:47 ` Tino Calancha
2020-08-07 12:05 ` Eli Zaretskii
2020-08-07 12:20 ` Bhavin Gandhi
2020-08-07 14:01 ` Tino Calancha
2020-08-07 15:06 ` Eli Zaretskii
2020-08-08 11:52 ` Tino Calancha
2020-08-09 14:26 ` Eli Zaretskii
2020-08-10 17:52 ` Tino Calancha
2020-08-12 16:50 ` Eli Zaretskii
2020-08-15 14:23 ` Tino Calancha
2020-08-05 18:24 ` Tino Calancha
2020-08-05 18:31 ` Bhavin Gandhi
2020-08-05 18:34 ` Tino Calancha
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=83k0yb999n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42655@debbugs.gnu.org \
--cc=bhavin7392@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=monnier@iro.umontreal.ca \
--cc=tino.calancha@gmail.com \
--cc=uyennhi.qm@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 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.