From: Eli Zaretskii <eliz@gnu.org>
To: Bhavin Gandhi <bhavin7392@gmail.com>
Cc: 42655@debbugs.gnu.org, eggert@cs.ucla.edu,
tino.calancha@gmail.com, uyennhi.qm@gmail.com,
monnier@iro.umontreal.ca
Subject: bug#42655: 27.1; iconify-frame on a Lucid build may stuck the frame
Date: Wed, 05 Aug 2020 21:43:50 +0300 [thread overview]
Message-ID: <83v9hx7x21.fsf@gnu.org> (raw)
In-Reply-To: <CAOn=hbcFzC8HdwJ_+TGbyxQQcK_NT5pVQUiv0ZuQP+yO0MxBsw@mail.gmail.com> (message from Bhavin Gandhi on Wed, 5 Aug 2020 22:53:15 +0530)
> From: Bhavin Gandhi <bhavin7392@gmail.com>
> Date: Wed, 5 Aug 2020 22:53:15 +0530
> Cc: tino.calancha@gmail.com, 42655@debbugs.gnu.org, eggert@cs.ucla.edu,
> monnier@iro.umontreal.ca, uyennhi.qm@gmail.com
>
> Thanks for the suggestion, here is the backtrace at the point when Emacs
> is stuck. Adding it as an attachment.
Thanks, this backtrace says that Emacs is just waiting for input.
Please try this now, after attaching the debugger:
(gdb) source /path/to/emacs/src/.gdbinit
(gdb) p selected_frame
(gdb) xtype
(replace "/path/to/emacs" with the actual absolute file name of the
Emacs source tree on your system). Then post here the results. And
please keep the GDB session running, don't exit it and don't kill
Emacs.
next prev parent reply other threads:[~2020-08-05 18:43 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 [this message]
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
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=83v9hx7x21.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.