GNU bug report logs - #60163
29.0.60; Error in post-command-hook (winner-save-old-configurations): (wrong-type-argument frame-live-p #<dead frame code action 0x563ea51cbf70>)

Previous Next

Package: emacs;

Reported by: 张云峰 <zhangyunfeng0101 <at> gmail.com>

Date: Sat, 17 Dec 2022 17:24:01 UTC

Severity: normal

Found in version 29.0.60

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: 张云峰 <zhangyunfeng0101 <at> gmail.com>
To: Po Lu <luangruo <at> yahoo.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, joaotavora <at> gmail.com, 60163 <at> 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: Tue, 20 Dec 2022 00:11:44 +0800

[Message part 1 (text/plain, inline)]
[image: 截图 2022-12-20 00-07-26.png]

Po Lu <luangruo <at> yahoo.com> 于2022年12月19日周一 22:28写道：

> 张云峰 <zhangyunfeng0101 <at> 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?
>

[Message part 2 (text/html, inline)]
[截图 2022-12-20 00-07-26.png (image/png, inline)]
This bug report was last modified 1 year and 252 days ago.

Previous Next

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