From: "夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>, Po Lu <luangruo@yahoo.com>
Cc: whainte@outlook.com, 55836@debbugs.gnu.org
Subject: bug#55836: 29.0.50; (iconify-frame) freezes buffer view under Wayland.
Date: Thu, 01 Sep 2022 19:26:52 +0800 [thread overview]
Message-ID: <877d2ne3nn.fsf@disroot.org> (raw)
In-Reply-To: <87a690z0fu.fsf@gnus.org>
I have tried to reproduce this but failed.
> Po Lu <luangruo@yahoo.com> writes:
>
>>> This breakpoint actually hits whenever the emacs frame gets focus, and
>>> makes debugging quite annoying.
Yes.
>>> Here's the strange thing: when a breakpoint is set there, the issue is
>>> not present; when the breakpoint
>>> is deleted and the procedure repeated, the issue reappears.
I tried:
1. In GDB, setup the breakpoint.
2. When the emacs got focus, switch to GDB prompt and run `continue'.
3. Switch back to the Emacs window, it should now stuck. Hit C-z, then
switch to GDB prompt and run `continue'.
4. Emacs should iconify itself. Deiconify it. It'll hit breakpoint
again. switch to GDB prompt and run `continue'.
5. Select Help in the menu bar. It'll hit breakpoint. switch to GDB
prompt and run `continue'.
6. The menu should pop up. run the Emacs tutorial.
7. Scroll in the Emacs window.
The Emacs tutorial can be scrolled.
However when I disable the breakpoint, When I deiconified the Emacs
window, it doesn't update even I tried to launch Emacs tutorial.
>> I didn't understand what you said, but I guess you should make the
>> breakpoint conditional on "FRAME_ICONIFIED_P (f)".
I tried, but GDB failed to setup this condition with:
No symbol "FRAME_ICONIFIED_P" in current context.
next prev parent reply other threads:[~2022-09-01 11:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 18:06 bug#55836: 29.0.50; (iconify-frame) freezes buffer view under Wayland koaaa.outlook
2022-06-08 0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-19 22:09 ` whainte
2022-06-20 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23 8:40 ` Lars Ingebrigtsen
2022-09-01 11:26 ` 夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-09-02 9:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 4:46 ` 夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 5:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <166219690756.47038.8534222496369366592@localhost>
2022-09-04 11:01 ` 夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-04 12:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-05 9:57 ` 夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-05 14:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] <c49677c5-8fe8-6038-7776-f42b5fba91e4@gmail.com>
2022-09-25 12:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <b5a17ec6-345-9df5-f5d3-1f1c803d6e8c@gmail.com>
2022-09-25 12:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <d3757b8e-8699-fe39-3534-f01789bedaf@gmail.com>
2022-09-26 0:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <c128677a-64b0-ba6f-4a6-df9a3e02b61@gmail.com>
2022-09-27 0:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-28 15:06 ` Tino Calancha
2022-09-29 0:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-30 12:36 ` Tino Calancha
2022-09-30 13:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-03 12:28 ` Tino Calancha
2022-11-09 12:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-10 10:59 ` Tino Calancha
2022-11-10 11:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=877d2ne3nn.fsf@disroot.org \
--to=bug-gnu-emacs@gnu.org \
--cc=55836@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=shadowrz@disroot.org \
--cc=whainte@outlook.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).