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 14:17:24 +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> <83h6vgv5r4.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="1398"; 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 15:18:42 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 1pU705-00006W-5Z for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 20 Feb 2023 15:18:41 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pU6zt-0002fP-By; Mon, 20 Feb 2023 09:18:31 -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 1pU6zV-0002bZ-DI for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 09:18:07 -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 1pU6zS-0004EM-7h for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 09:18:05 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pU6zS-0006Y2-3F for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 09:18: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 14:18: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.167690264925116 (code B ref 61514); Mon, 20 Feb 2023 14:18:02 +0000 Original-Received: (at 61514) by debbugs.gnu.org; 20 Feb 2023 14:17:29 +0000 Original-Received: from localhost ([127.0.0.1]:51107 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU6yv-0006X1-Er for submit@debbugs.gnu.org; Mon, 20 Feb 2023 09:17:29 -0500 Original-Received: from heytings.org ([95.142.160.155]:37020) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU6yr-0006Wr-PS for 61514@debbugs.gnu.org; Mon, 20 Feb 2023 09:17:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1676902644; bh=SSmH4H3iYL/FTJTzeYgvjrDCZnd4dTUIi9t/vYYHmRI=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=plrQNbrsyARMGeyVSDFUv9Bn7LERp10yCeiCQShS3Rqak8ZNpd/pAxBogkYpYZVZs StRIru0ty7DXRfYpkh2IrCLc62M26V1AdxcMqNsSyeor7S9aUpWWpKxQFtaSEmWzIT hZ0soJnMAHezWuuVp21le/UUCRRWjcJBkQAclViHTp/Oa8a/G2dc89JISgO08rCzNL 7vwUR6VY1QXHaHqxoEHeGTVtIrgdyS5FKdFg6InzDN7ZnYhUqbeLXYMwzDaevS2mS9 dbCCHywDJh6Rr6pQatSHUDyy76YX07kWAjaGgljHaWqvG0IPiG4X7UzjRWSN+jRuca qIJ30ZriE9/PQ== In-Reply-To: <83h6vgv5r4.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:256181 Archived-At: >>> 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. > > I don't trust people who don't build Emacs and run it under GDB to use > such a variable judiciously. > In the current patch it is automatically capped to a maximum value. It could also be automatically reset to a minimum value (say 1000 or 500 or 100). I just tried to set it to 500 in my configuration during a few minutes, and did not see any errors, so I don't see what could go fundamentally wrong if we give users control on that threshold. It would have been much easier to debug this bug by asking Mark "could you please try to temporarily set regexp-max-backtracking-depth to 1000 and see if that fixes the bug?". This bug report was easy to reproduce, so that wasn't necessary, but it would be for bug reports from users with more complex setup.