From: Eli Zaretskii <eliz@gnu.org>
To: Jos de Kloe <kloe0040@planet.nl>
Cc: 58164@debbugs.gnu.org
Subject: bug#58164: 28.1; keybinding C-z to suspend-frame in fvwm windowmanager seems to get lost after first use.
Date: Mon, 03 Oct 2022 19:47:18 +0300 [thread overview]
Message-ID: <83y1twyhux.fsf@gnu.org> (raw)
In-Reply-To: <40dcca87-666a-2c21-2e9d-5cf82fb4b8b3@planet.nl> (message from Jos de Kloe on Mon, 3 Oct 2022 08:37:06 +0200)
> Date: Mon, 3 Oct 2022 08:37:06 +0200
> Cc: 58164@debbugs.gnu.org
> From: Jos de Kloe <kloe0040@planet.nl>
>
> second time I hit C-z:
>
> Thread 1 "emacs" hit Breakpoint 1, x_iconify_frame (f=0xe46c70) at
> xterm.c:11976
> 11976 {
> (gdb) n
> 11982 if (FRAME_DISPLAY_INFO (f)->highlight_frame == f)
> (gdb) n
> 11983 FRAME_DISPLAY_INFO (f)->highlight_frame = 0;
> (gdb) n
> 11985 if (FRAME_ICONIFIED_P (f))
> (gdb) n
> Ffuncall (nargs=1, args=args@entry=0x7fffffffd258) at eval.c:3048
> 3048 lisp_eval_depth--;
> (gdb) n
> 3049 if (backtrace_debug_on_exit (specpdl + count))
> (gdb) n
> 3051 specpdl_ptr--;
> (gdb) n
> 3052 return val;
> (gdb) n
>
> I hope this helps to zoom in on the problem.
It gives a hint. Can you type "bt" before you type "n" here:
> 11985 if (FRAME_ICONIFIED_P (f))
> (gdb) n
and show the resulting backtrace? Also, type "bt" _after_ you type
"n" there and see this line:
> Ffuncall (nargs=1, args=args@entry=0x7fffffffd258) at eval.c:3048
> 3048 lisp_eval_depth--;
You see, FRAME_ICONIFIED_P doesn't call Ffuncall, and there's no such
call anywhere in sight inside x_iconify_frame. So either the macro
FRAME_ICONIFIED_P somehow signaled an error (which I don't think can
happen), or something else kicked us out of the function when we tried
to see if the frame is already iconified. The question is: what did
kick us out and why?
next prev parent reply other threads:[~2022-10-03 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 14:32 bug#58164: 28.1; keybinding C-z to suspend-frame in fvwm windowmanager seems to get lost after first use Jos de Kloe
2022-09-29 17:41 ` Eli Zaretskii
2022-09-30 6:45 ` Jos de Kloe
2022-09-30 6:58 ` Eli Zaretskii
2022-10-03 5:52 ` Jos de Kloe
2022-10-03 6:37 ` Jos de Kloe
2022-10-03 16:47 ` Eli Zaretskii [this message]
2022-10-03 17:39 ` Jos de Kloe
2022-10-03 17:56 ` Eli Zaretskii
2022-10-04 0:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 1:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 6:45 ` Jos de Kloe
2022-10-04 8:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y1twyhux.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58164@debbugs.gnu.org \
--cc=kloe0040@planet.nl \
/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.