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 05:29:12 +0300 [thread overview]
Message-ID: <83sgd08q2v.fsf@gnu.org> (raw)
In-Reply-To: <874kpgj4z5.fsf@gmail.com> (message from Tino Calancha on Wed, 05 Aug 2020 20:57:18 +0200)
> From: Tino Calancha <tino.calancha@gmail.com>
> Cc: Bhavin Gandhi <bhavin7392@gmail.com>, uyennhi.qm@gmail.com,
> 42655@debbugs.gnu.org, eggert@cs.ucla.edu, monnier@iro.umontreal.ca
> Date: Wed, 05 Aug 2020 20:57:18 +0200
>
> (gdb)
> p selected_frame
> &"p selected_frame\n"
> ~"$1 = XIL(0x14f0835)\n"
> ^done
> (gdb)
> xtype
> &"xtype\n"
> ~"Lisp_Vectorlike"
> ~"\n"
> ~"PVEC_FRAME"
> ~"\n"
> ^done
> (gdb)
OK, now the important part:
(gdb) p XFRAME (selected_frame)
(gdb) p *$
The last command should display all the members of 'struct frame' that
correspond to the frame which doesn't redisplay.
Just to be sure: you are typing these commands in a situation where
you did NOT yet create another frame, this is the same frame which was
iconified by C-z, right? I want to be sure we display the problematic
frame, not some other one.
Thanks.
next prev parent reply other threads:[~2020-08-06 2:29 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 [this message]
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
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
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=83sgd08q2v.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 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).