From: Daniel Colascione <dancol@dancol.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 24905@debbugs.gnu.org
Subject: bug#24905: 25.1.50; Lock-up in python-mode
Date: Tue, 08 Nov 2016 14:45:07 -0800 [thread overview]
Message-ID: <r0254m3h6170.fsf@dancol.org> (raw)
In-Reply-To: <r0258tst61hn.fsf@dancol.org> (Daniel Colascione's message of "Tue, 08 Nov 2016 14:38:44 -0800")
On Tue, Nov 08 2016, Daniel Colascione wrote:
> On Tue, Nov 08 2016, Philipp Stephani wrote:
>> echo ' "' > /tmp/a.py
>> emacs -Q /tmp/a.py
>>
>> Emacs locks up immediately.
>> Given that this is so easy to trigger, it should block the 25.2
>> release.
>
> Can repro. Thanks for coming up with a small testcase.
FWIW, the Lisp traceback is this:
"syntax-ppss" (0xffff2978)
"python-info-line-ends-backslash-p" (0xffff2e80)
"python-nav-beginning-of-statement" (0xffff3388)
"python-info-beginning-of-statement-p" (0xffff3840)
"python-info-beginning-of-block-p" (0xffff3d38)
"python-nav--forward-sexp" (0xffff43d8)
"python-nav-forward-sexp" (0xffff4918)
"python-nav-backward-sexp" (0xffff4e20)
"python-info-docstring-p" (0xffff5378)
"python-font-lock-syntactic-face-function" (0xffff5850)
"font-lock-fontify-syntactically-region" (0xffff5e00)
"font-lock-default-fontify-region" (0xffff6380)
"font-lock-fontify-region" (0xffff6858)
0x1c27368 PVEC_COMPILED
"run-hook-wrapped" (0xffff6f30)
"jit-lock--run-functions" (0xffff74b0)
"jit-lock-fontify-now" (0xffff7b08)
"jit-lock-function" (0xffff80b8)
"redisplay_internal (C function)" (0x0)
We're actually finishing GC, by the way: this isn't a problem with
the alloc.c guts, fortunately. We're just generating tons of
garbage. I've seen infloops in python.el's syntactic analysis
before. This one looks worse than usual because it happens in redisplay.
(Maybe redisplay should impose time limits on lisp that it runs?)
next prev parent reply other threads:[~2016-11-08 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 22:30 bug#24905: 25.1.50; Lock-up in python-mode Philipp Stephani
2016-11-08 22:38 ` Daniel Colascione
2016-11-08 22:45 ` Daniel Colascione [this message]
2016-11-08 23:34 ` Daniel Colascione
2016-11-09 15:42 ` Eli Zaretskii
2016-11-09 0:27 ` npostavs
2016-11-09 3:38 ` Eli Zaretskii
2016-11-09 3:44 ` Noam Postavsky
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=r0254m3h6170.fsf@dancol.org \
--to=dancol@dancol.org \
--cc=24905@debbugs.gnu.org \
--cc=p.stephani2@gmail.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).