From: 张云峰 <zhangyunfeng0101@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
joaotavora@gmail.com, 60163@debbugs.gnu.org
Subject: bug#60163: 29.0.60; Error in post-command-hook (winner-save-old-configurations): (wrong-type-argument frame-live-p #<dead frame code action 0x563ea51cbf70>)
Date: Mon, 19 Dec 2022 23:49:13 +0800 [thread overview]
Message-ID: <CA+cG9GxQosgvkgPyuXp+WQ_rcnQE1cA_CC0_wrtUEp8AVfT_Dw@mail.gmail.com> (raw)
In-Reply-To: <87h6xreadm.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]
Done.
[Detaching after vfork from child process 650535]
[Detaching after vfork from child process 650536]
[Detaching after vfork from child process 650537]
[Detaching after vfork from child process 650538]
[Detaching after vfork from child process 650539]
[Detaching after vfork from child process 650540]
[Detaching after vfork from child process 650541]
[Detaching after vfork from child process 650542]
[Detaching after vfork from child process 650543]
[Detaching after vfork from child process 650544]
[Detaching after vfork from child process 650545]
[Detaching after vfork from child process 650546]
[Detaching after vfork from child process 650547]
[Detaching after vfork from child process 650729]
[Detaching after vfork from child process 650730]
[Detaching after vfork from child process 650731]
[Detaching after vfork from child process 650732]
Thread 1 "emacs" hit Breakpoint 1, delete_frame (frame=0x555558c02e05,
force=0x0) at frame.c:1932
1932 {
(gdb) l
1927 * unconditionally. x_connection_closed and delete_terminal use this.
1928 * Any other value of FORCE implements the semantics described for
1929 * Fdelete_frame. */
1930 Lisp_Object
1931 delete_frame (Lisp_Object frame, Lisp_Object force)
1932 {
1933 struct frame *f = decode_any_frame (frame);
1934 struct frame *sf;
1935 struct kboard *kb;
1936 Lisp_Object frames, frame1;
(gdb) c
Continuing.
[Detaching after vfork from child process 650742]
[Detaching after vfork from child process 650964]
*==================================================> here emacs can't
edit, no cursor( cursor in edit area just disappeared), but mouse pointer
can select text in emacs and hover event also can trigger.*
*What should I do next ?*
Po Lu <luangruo@yahoo.com> 于2022年12月19日周一 22:28写道:
> 张云峰 <zhangyunfeng0101@gmail.com> writes:
>
> > Thanks for your quick reply.
> >
> > Yes, I did, the author of lsp-bridge thinks that this bug belongs to
> emacs itself.
> > What's confusing is that lsp-bridge works very well in emacs28 and
> emacs29 without pgtk feature.
> > And I think that even if it is a bug in a third-party library, it should
> not cause emacs to be unable to edit.
>
> If you put a breakpoint with GDB on delete_frame set to only print a
> backtrace and then continue (would someone else please explain the
> procedure, as it's 10:30 PM here), what is printed immediately before
> the error?
>
[-- Attachment #2: Type: text/html, Size: 3054 bytes --]
next prev parent reply other threads:[~2022-12-19 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 14:35 bug#60163: 29.0.60; Error in post-command-hook (winner-save-old-configurations): (wrong-type-argument frame-live-p #<dead frame code action 0x563ea51cbf70>) 张云峰
2022-12-17 17:54 ` Eli Zaretskii
[not found] ` <CA+cG9Gw0CJNsfWViAbU8Zoooo4OJhynhD5k4y0dy_J=Uuu-F-Q@mail.gmail.com>
2022-12-19 12:15 ` Eli Zaretskii
2022-12-19 12:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-19 12:58 ` Eli Zaretskii
2022-12-19 13:32 ` 张云峰
2022-12-19 14:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-19 15:49 ` 张云峰 [this message]
2022-12-20 1:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-20 2:25 ` 张云峰
2022-12-19 16:11 ` 张云峰
2022-12-19 14:12 ` 张云峰
2022-12-20 8:12 ` martin rudalics
[not found] ` <CA+cG9GwuyL+UxC_L5aRC+MJLFzLMrhYDzOVE8SmJzRrHTmB0NQ@mail.gmail.com>
2022-12-21 9:22 ` martin rudalics
2022-12-21 14:50 ` 张云峰
2022-12-21 17:06 ` martin rudalics
2022-12-22 2:34 ` 张云峰
2022-12-22 10:15 ` martin rudalics
2023-06-07 1:34 ` Michael Heerdegen
2023-09-11 18:10 ` Stefan Kangas
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=CA+cG9GxQosgvkgPyuXp+WQ_rcnQE1cA_CC0_wrtUEp8AVfT_Dw@mail.gmail.com \
--to=zhangyunfeng0101@gmail.com \
--cc=60163@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--cc=luangruo@yahoo.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).