From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#61514: 30.0.50; sadistically long xml line hangs emacs Date: Mon, 20 Feb 2023 12:40:54 +0000 Message-ID: References: <87lel0c65v.fsf@everybody.org> <838rgvymcd.fsf@gnu.org> <886c06e50e9cfacb7954@heytings.org> <83h6vixik1.fsf@gnu.org> <886c06e50e707ab83560@heytings.org> <886c06e50e876183758c@heytings.org> <83zg98v7qs.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4344"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mah@everybody.org, 61514@debbugs.gnu.org, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Feb 20 13:41:24 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 1pU5Tw-0000wV-99 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 20 Feb 2023 13:41:24 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pU5Ti-0000Zs-ER; Mon, 20 Feb 2023 07:41:10 -0500 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 1pU5Ta-0000Yp-J7 for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 07:41:02 -0500 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 1pU5Ta-0006C5-AL for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 07:41:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pU5Ta-0001Op-5N for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 07:41:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 20 Feb 2023 12:41:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61514 X-GNU-PR-Package: emacs Original-Received: via spool by 61514-submit@debbugs.gnu.org id=B61514.16768968585355 (code B ref 61514); Mon, 20 Feb 2023 12:41:02 +0000 Original-Received: (at 61514) by debbugs.gnu.org; 20 Feb 2023 12:40:58 +0000 Original-Received: from localhost ([127.0.0.1]:50846 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU5TV-0001OJ-QA for submit@debbugs.gnu.org; Mon, 20 Feb 2023 07:40:58 -0500 Original-Received: from heytings.org ([95.142.160.155]:36856) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU5TU-0001OA-1f for 61514@debbugs.gnu.org; Mon, 20 Feb 2023 07:40:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1676896855; bh=fH9LmQB5CCNfZQ1xC+pIAIEj0DqTY8YGL9YEqY0NbKg=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=0/OlBLSgJR9qpq+P+GUUcapye6S+N93ajUagWbhSKBGelEfVXIa+Ny5+DmElcgBo/ PF/POqMxvgBcQ1XrnOkQwupTig+SLxDx0PgDn3BM7duDtKgh6D+3HsUsrXF6O1StCt ZnhpS0mac1vhHF8LHY3uhsjqw5BCuFfxn65VLfRoGiegGl8aXqXHSYKIOOXuEgN9z8 NFIWsq1JBxoBxup228mV7Ti5LEM7ZzJioFl/ufayQkPWfRfMe/ypEIUIks40XN+Iti 3eVNaUXvCMxSOlUwMac2TmDDMo15q2UB5bGbbqD5y8cEvAUUNofOVMwYMGabEpTiy3 fZqlb3eiAbqNg== In-Reply-To: <83zg98v7qs.fsf@gnu.org> 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:256156 Archived-At: >> BTW, this makes me wonder why emacs_re_max_failures is not accessible >> from Elisp. I think it would be very useful, if only for debugging >> purposes. And perhaps let-binding it to a lower value around some >> potentially (or actually) problematic regexps would be a good way to >> prevent or fix bugs such as the current one. > > If we know which regexps cause problems, shouldn't we instead fix those > regexps, or change how we use them? > If we know how and where to fix them, that's better of course. If we don't (and frankly when I look at that regexp I have no idea how it could be fixed), limiting the backtracking depth to a more reasonable value is better than not fixing the bug. > > For debugging purposes, you can set the value in the debugger after > starting Emacs, or with a breakpoint just before calling the problematic > code. > That's only true for the (very) few of us who are comfortable building Emacs and running it under GDB (and even for them it's much easier to just change the value with a setq). If regexp-max-backtracking-depth had been present, everyone could easily have tried to set it to some lower value.