GNU bug report logs - #42655
27.1; iconify-frame on a Lucid build may stuck the frame

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Tino Calancha <tino.calancha <at> gmail.com>
Cc: 42655 <at> debbugs.gnu.org, eggert <at> cs.ucla.edu, uyennhi.qm <at> gmail.com, bhavin7392 <at> gmail.com, monnier <at> 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

> From: Tino Calancha <tino.calancha <at> gmail.com>
> Cc: Bhavin Gandhi <bhavin7392 <at> gmail.com>,  42655 <at> debbugs.gnu.org,
>   eggert <at> cs.ucla.edu,  uyennhi.qm <at> gmail.com,  monnier <at> 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 <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.