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:06:12 +0000 Message-ID: References: <87lel0c65v.fsf@everybody.org> <838rgvymcd.fsf@gnu.org> <831qmkwmux.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23574"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 61514@debbugs.gnu.org, mah@everybody.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Feb 20 15:07:18 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 1pU6p3-0005r0-Fx for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 20 Feb 2023 15:07:17 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pU6oq-0001Lh-Iw; Mon, 20 Feb 2023 09:07:04 -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 1pU6oo-0001LF-QI for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 09:07: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 1pU6oo-0001OC-H5 for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 09:07:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pU6oo-0003pa-3I for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 09:07: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:07: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.167690197714656 (code B ref 61514); Mon, 20 Feb 2023 14:07:02 +0000 Original-Received: (at 61514) by debbugs.gnu.org; 20 Feb 2023 14:06:17 +0000 Original-Received: from localhost ([127.0.0.1]:51056 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU6o5-0003oK-AC for submit@debbugs.gnu.org; Mon, 20 Feb 2023 09:06:17 -0500 Original-Received: from heytings.org ([95.142.160.155]:36978) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU6o1-0003oA-La for 61514@debbugs.gnu.org; Mon, 20 Feb 2023 09:06:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1676901972; bh=FvhcRnuixySRchrq0RouepN0WcwJrEJPVyQWn8KoRfo=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=ihFYcl2DWvIyDekJPNOZnB46U+aabo3OucGmjWQPB3qhWsLl/J1AiP77duvmWJIE7 aAC1lVloFQ5yJs8cuuma1iIFWUOmmASdoQaTtRK44BWdZHzwV8Qt+1FJagErhtoPP3 zFq7S1PlltzCodASqFIzaUmT1owyCdjCv/s1q50wSgWjVh88Os55ugShP4oRAC/aI0 tRTGe7ce2EjZvevpF13QLKrye0YEi3ZE3czjmWHuQS3q4OFovGNveDfM8tkpzZA4Pl /fUT/NaznKTHxhcLZdrOvagoBQNbI37c+x5SLNn4BGeLv21WYrRW4M1c57N7v6QbQJ X7SZ5Fw8A4+bA== 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:256174 Archived-At: > > I think it does. E.g. there's a chance that using "[^<>\n]+?\\<" > instead of "[^<>\n]+?" avoids the hang (not sure if it's the right thing > to do for all the regexp that can be returned by `xmltok-attribute`, > tho). > That does work, indeed. Using e.g. "[^<>\n]\\{1,100\\}?" also works (but is not as efficient). Perhaps Mark (who added xmltok.el to Emacs in 2007) can help here to determine what the right thing is? > > And for the stack overflow I haven't yet found its origin. > There is no stack overflow here, AFAIU. It's simply that the prepended regexp matches one or more (without any upper bound) characters except "<>\n", which means that we backtrack _a lot_ when the line is long.