From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: rhstanton@berkeley.edu, 54996@debbugs.gnu.org
Subject: bug#54996: Emacs hangs when editing Python code with debug-on-error set to t
Date: Mon, 18 Apr 2022 16:17:46 +0200 [thread overview]
Message-ID: <CAArVCkQN7o5jiMHXR7NqzJa+YnhMurp5p3pCWuqLtFr68i0NqA@mail.gmail.com> (raw)
In-Reply-To: <87o80yiqqu.fsf@gnus.org>
Am Mo., 18. Apr. 2022 um 13:19 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> But here we go -- I instrumented Fsignal after loading everything.
>
> gdb) xbacktrace
> "signal" (0xeabde738)
> "error" (0xffff8378)
> "apply" (0xeabde6e0)
> "cl--assertion-failed" (0xeabde668)
> "python-nav-end-of-statement" (0xeabde620)
> "python-info-end-of-statement-p" (0xeabde5f0)
> "python-info-end-of-block-p" (0xeabde598)
> "python-nav--forward-sexp" (0xeabde518)
> "python-nav-forward-sexp" (0xeabde4c0)
> "python-nav-backward-sexp" (0xeabde468)
> "python-info-docstring-p" (0xeabde408)
> "python-font-lock-syntactic-face-function" (0xeabde3a8)
> "font-lock-fontify-syntactically-region" (0xeabde320)
> "font-lock-default-fontify-region" (0xeabde2b0)
> "font-lock-fontify-region" (0xeabde240)
> 0x566c35a8 PVEC_COMPILED
> "run-hook-wrapped" (0xeabde1c8)
>
> I've now fixed this by avoiding cl-assert (which probably should never
> be used inside a function called from font-lock).
>
The assertion was added to protect against a subtle but nasty bug, see
commit 4fbd330fae54a9c45d4a717127aa86d75e9938d5. Please don't remove
the assertion without first ensuring that the bug won't reoccur.
next prev parent reply other threads:[~2022-04-18 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 20:16 bug#54996: Emacs hangs when editing Python code with debug-on-error set to t Richard Stanton
2022-04-17 20:43 ` Lars Ingebrigtsen
2022-04-18 5:46 ` Eli Zaretskii
2022-04-18 9:45 ` Lars Ingebrigtsen
2022-04-18 10:02 ` Eli Zaretskii
2022-04-18 11:07 ` Lars Ingebrigtsen
2022-04-18 11:18 ` Lars Ingebrigtsen
2022-04-18 14:17 ` Philipp Stephani [this message]
2022-04-18 14:23 ` Lars Ingebrigtsen
2022-04-18 10:56 ` Daniel Martín 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=CAArVCkQN7o5jiMHXR7NqzJa+YnhMurp5p3pCWuqLtFr68i0NqA@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=54996@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rhstanton@berkeley.edu \
/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.