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: Bhavin Gandhi <bhavin7392 <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: uyennhi.qm <at> gmail.com, 42655 <at> debbugs.gnu.org, eggert <at> cs.ucla.edu, monnier <at> iro.umontreal.ca, tino.calancha <at> gmail.com
Subject: bug#42655: 27.1; iconify-frame on a Lucid build may stuck the frame
Date: Wed, 5 Aug 2020 00:23:09 +0530

On Tue, 4 Aug 2020 at 22:11, Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> And when you do create a new frame, do you see the redraw-display
> command in the command history?  Also, what does "C-h l" show in that
> other frame?

Yes, I can see the redraw-display command in command-history. This is
what "C-h l" shows.

--8<---------------cut here---------------start------------->8---
 C-z                    ;; suspend-frame
 M-x                    ;; execute-extended-command
 r                      ;; self-insert-command
 e                      ;; self-insert-command
 d                      ;; self-insert-command
 r                      ;; self-insert-command
 <return>               ;; minibuffer-complete-and-exit
 C-x 5 2                ;; make-frame-command
 ;; handle-switch-frame
 C-h l                  ;; view-lossage
--8<---------------cut here---------------end--------------->8---

> If you now attach a debugger to Emacs, what does the backtrace show?

Is running "gdb -i=mi -p PID" enough to generate this backtrace?

Previous Next

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