From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: James Mazer Newsgroups: gmane.emacs.bugs Subject: bug#63363: 28.2; emacs freezes opening python file w/ unclosed quotes Date: Wed, 10 May 2023 17:01:02 -0600 Message-ID: References: <17BB823F-A919-44FB-87E1-1CAC9BD7426B@netyu.xyz> <83lehzcaq0.fsf@gnu.org> <83v8h2bwrw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000003f0b2a05fb5ed9d7" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37514"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 63363@debbugs.gnu.org To: Ruijie Yu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 11 01:02:25 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pwspE-0009Yi-Qf for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 11 May 2023 01:02:24 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pwsot-0007Ta-Vu; Wed, 10 May 2023 19:02:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pwsos-0007TF-Gi for bug-gnu-emacs@gnu.org; Wed, 10 May 2023 19:02:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pwsos-0008WP-83 for bug-gnu-emacs@gnu.org; Wed, 10 May 2023 19:02:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pwsos-0005wP-1m for bug-gnu-emacs@gnu.org; Wed, 10 May 2023 19:02:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: James Mazer Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 10 May 2023 23:02:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63363 X-GNU-PR-Package: emacs Original-Received: via spool by 63363-submit@debbugs.gnu.org id=B63363.168375968222780 (code B ref 63363); Wed, 10 May 2023 23:02:02 +0000 Original-Received: (at 63363) by debbugs.gnu.org; 10 May 2023 23:01:22 +0000 Original-Received: from localhost ([127.0.0.1]:49211 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pwsoD-0005vL-V2 for submit@debbugs.gnu.org; Wed, 10 May 2023 19:01:22 -0400 Original-Received: from mail-yb1-f182.google.com ([209.85.219.182]:55445) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pwsoB-0005v6-P5 for 63363@debbugs.gnu.org; Wed, 10 May 2023 19:01:20 -0400 Original-Received: by mail-yb1-f182.google.com with SMTP id 3f1490d57ef6-b9a6869dd3cso10214088276.2 for <63363@debbugs.gnu.org>; Wed, 10 May 2023 16:01:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683759674; x=1686351674; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iCm3GOVYH8Y6wzhYJYojY0cT1Ii8UfedqpX8R9WcbBc=; b=J/OOVPo1gfM2zLrUVN6PYDfT2DD2l8nIVqMdIBb5t0O+lW2ge7O0X4dDuU06aveNDj K14IfnCErk8LNLXZFpg7Gy+ctY64aQJ4LoKVtr4pn7Tl6uC/eY7qKqTTmeN4rGYA0eaZ 0BaAgmS2O4eFjS2STfJdZ5t/lHA8JDEcHbomTnnZGdOJFEmULv0cfeMOH0BFSy84/0rF fdH62utVbCV+9EWqBNsxALnvYC0Gu4LK0pUERhD97LB77uiOunr5y8zKZcVQvNhvt+Cm sxE2pz5GTDKVWJ6v7YguYH2kY6vgC0BvL134cz5LSgik/TTWLqdEd0Dpv+qEoCD+rzg9 EfCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683759674; x=1686351674; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iCm3GOVYH8Y6wzhYJYojY0cT1Ii8UfedqpX8R9WcbBc=; b=OPV9hsAG/cyJCHMz2EiYCnTZweeZHZyNHVpQBCH8NTAsvbBqhNM4cQ7SEx1bqmC6CH A8sZJcS8fq9tizw8G9yWU5yS4WfUmwrDMj4Yp9+1R2QN5HlHIaH1l1gDIcOkrrGTXaZK IFuExElkfzFryc1FwJK8aNa8J8L92oc60VTwhfgipormnmnwpXNYshHFbACZDFZEfDYz sBoawVI5QTmaaZJhjOC+70T80ARTdDo7/QYsYNgCHpewrT+duplwI7Y6QQw2Eg0vwY0H OuA0vJ2xKTXc0dYulTSWbFv+7J2skNvi2NE1VjbsyvBMNSB1A60h+43YJZSpPFMYchXq QCxw== X-Gm-Message-State: AC+VfDyXeaIDfobD3Y3hPxXvI+J2AbxCVI/POoVLJi+nrd3RPmo6rSgZ 6AvUCFooC9zO2/xK1JEpEl9g+YnO+vWmWDGxyDg= X-Google-Smtp-Source: ACHHUZ6t3Q/jXUdtAdR1mVWI9a8/Wp3mmZwBb+8uUkTrVsYO4ichKyL531qwZNH2Ir8PsxdUHsC44QZYqrnNbysXxtc= X-Received: by 2002:a25:d74b:0:b0:ba6:954c:870a with SMTP id o72-20020a25d74b000000b00ba6954c870amr856929ybg.17.1683759673833; Wed, 10 May 2023 16:01:13 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:261531 Archived-At: --0000000000003f0b2a05fb5ed9d7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Just confirmed that with an emacs 29.0.90 snap (beta) I'm not seeing the lock up. So it appears to be fixed downstream, but would be nice to be able to fix in 28 until 29 is actually released :-) On Tue, May 9, 2023 at 9:23=E2=80=AFAM James Mazer w= rote: > Yes, seems to be the same issue. I just tried replicating his trigger and > locked up an emacs window.. here's the backtrace after sigusr2: > >> Debugger entered--entering a function: >> * #f(compiled-function () #)() >> syntax-ppss() >> python-nav-end-of-statement() >> python-nav-end-of-block() >> python-info-statement-ends-block-p() >> python-nav--forward-sexp(-1 nil nil) >> python-nav-forward-sexp(-1 nil nil) >> python-nav-backward-sexp() >> python-info-docstring-p((0 nil 390 34 nil nil 0 nil 427 nil nil)) >> python-font-lock-syntactic-face-function((0 nil 390 34 nil nil 0 nil >> 427 nil nil)) >> font-lock-fontify-syntactically-region(180 1700 nil) >> font-lock-default-fontify-region(184 1684 nil) >> font-lock-fontify-region(184 1684) >> #f(compiled-function (fun) #> 0x19ba0a4f10e54dbd>)(font-lock-fontify-region) >> jit-lock--run-functions(184 1684) >> jit-lock-fontify-now(184 1684) >> jit-lock-function(184) >> redisplay_internal\ \(C\ function\)() > > > I'll see if I can spin up a version of 29. Been a while since I compiled > emacs from scratch... I'm actually surprised that there aren't packages f= or > 28 and 29 more readily available for ubuntu. Not sure what's up with that= . > > > On Mon, May 8, 2023 at 9:09=E2=80=AFPM Ruijie Yu wrote= : > >> >> James Mazer writes: >> >> > Don't have time right now to do a custom build, but as sanity check, I >> just quickly pulled the 28.2 gnu.org.emacs flatpak and tried that and I = get >> > exactly the same issue, so it doesn't appear to be specific to the sna= p >> build. I can't find a 29 snap or flatpak to test, though. >> >> There is also another bug report (closed as fixed on 29), #62794, that I >> think is the same as this report and #62325. In particular, see this >> message within that bug report: >> >> msgid:ZDdE/j6dDbhCw1QF@nicku.org >> https://mail.gnu.org/archive/html/bug-gnu-emacs/2023-04/msg00798.html >> >> What Nick described in #62794 sounds exactly the same as your issue and >> Eli's observation: that only _some type(s) of_ python files trigger the >> error. I, as well as Eli, were able to reproduce the issue of #62794 >> via using the file Nick attached in that message. >> >> James, can you confirm that Nick's issue on #62794 is exactly the same >> as yours in this bug report, and that you can also reproduce the issue >> using Nick's attachment from that message? >> >> And also, if you want to get a version of 29 to test, you can either get >> the pretest or clone the code and run "make". The resultant emacs >> binary is located at "src/emacs". Let me know if this is unclear. >> >> -- >> Best, >> >> >> RY >> > > > -- > James Mazer > mazerj@gmail.com > > --=20 James Mazer mazerj@gmail.com --0000000000003f0b2a05fb5ed9d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just confirmed that with an emacs 29.0.90 snap (beta) I= 9;m not seeing the lock up. So it appears to be fixed downstream, but would= be nice to be able to fix in 28 until 29 is actually released :-)

=

On Tue, May 9, 2023 at 9:23=E2=80=AFAM James Mazer <mazerj2006@gmail.com> wrote:
Yes, se= ems to be the same issue. I just tried replicating his trigger and locked u= p an emacs window.. here's the backtrace after sigusr2:
Debugger entered--entering a functi= on:
* #f(compiled-function () #<bytecode 0xb893e2c8c539dfa>)()
= =C2=A0 syntax-ppss()
=C2=A0 python-nav-end-of-statement()
=C2=A0 pyth= on-nav-end-of-block()
=C2=A0 python-info-statement-ends-block-p()
=C2= =A0 python-nav--forward-sexp(-1 nil nil)
=C2=A0 python-nav-forward-sexp(= -1 nil nil)
=C2=A0 python-nav-backward-sexp()
=C2=A0 python-info-docs= tring-p((0 nil 390 34 nil nil 0 nil 427 nil nil))
=C2=A0 python-font-loc= k-syntactic-face-function((0 nil 390 34 nil nil 0 nil 427 nil nil))
=C2= =A0 font-lock-fontify-syntactically-region(180 1700 nil)
=C2=A0 font-loc= k-default-fontify-region(184 1684 nil)
=C2=A0 font-lock-fontify-region(1= 84 1684)
=C2=A0 #f(compiled-function (fun) #<bytecode 0x19ba0a4f10e54= dbd>)(font-lock-fontify-region)
=C2=A0 jit-lock--run-functions(184 16= 84)
=C2=A0 jit-lock-fontify-now(184 1684)
=C2=A0 jit-lock-function(18= 4)
=C2=A0 redisplay_internal\ \(C\ function\)()
=C2=A0<= /div>
I'll see if I can spin up a version of 29. Been a while since= I compiled emacs from scratch... I'm actually surprised that there are= n't packages for 28 and 29 more readily available for ubuntu. Not sure = what's up with that.


On Mon, May 8, 2023 at 9:09=E2= =80=AFPM Ruijie Yu <ruijie@netyu.xyz> wrote:

James Mazer <m= azerj2006@gmail.com> writes:

> Don't have time right now to do a custom build, but as sanity chec= k, I just quickly pulled the 28.2 gnu.org.emacs flatpak and tried that and = I get
> exactly the same issue, so it doesn't appear to be specific to the= snap build. I can't find a 29 snap or flatpak to test, though.

There is also another bug report (closed as fixed on 29), #62794, that I think is the same as this report and #62325.=C2=A0 In particular, see this<= br> message within that bug report:

msgid:ZDdE/j6dDb= hCw1QF@nicku.org
https://mail.gnu.org/archive/ht= ml/bug-gnu-emacs/2023-04/msg00798.html

What Nick described in #62794 sounds exactly the same as your issue and
Eli's observation: that only _some type(s) of_ python files trigger the=
error.=C2=A0 I, as well as Eli, were able to reproduce the issue of #62794<= br> via using the file Nick attached in that message.

James, can you confirm that Nick's issue on #62794 is exactly the same<= br> as yours in this bug report, and that you can also reproduce the issue
using Nick's attachment from that message?

And also, if you want to get a version of 29 to test, you can either get the pretest or clone the code and run "make".=C2=A0 The resultant= emacs
binary is located at "src/emacs".=C2=A0 Let me know if this is un= clear.

--
Best,


RY


--
=
James Mazer



--
--0000000000003f0b2a05fb5ed9d7--