unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 18577@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>,
	Alan Mackenzie <acm@muc.de>
Subject: bug#18577: Regexp I-search: [(error Stack overflow in regexp matcher)]
Date: Thu, 27 Nov 2014 09:44:36 +0100	[thread overview]
Message-ID: <878uixm3rf.fsf@thinkpad-t440p.tsdh.org> (raw)
In-Reply-To: <jwv38bbsme9.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Sun, 28 Sep 2014 13:35:30 -0400")

We have a similar bug report for AUCTeX/RefTeX, although the regex
doesn't look that bad as Alan's.

Too reproduce, create a file with 10000 lines with the word foo, and
evaluate this:

  (re-search-forward "^[^%]*\\\\usepackage.*{biblatex}" nil t)

Here, there's no double-* or nested-* but still you get a stack overflow
in the regexp matcher.

Ah, the problem here is that [^%] also matches \n.  I've just seen that
this regex has already been fixed to

  "^[^%\n]*?\\\\usepackage.*{biblatex}"

on master, and I've backported the fix to the emacs-24 branch.

Bye,
Tassilo





  reply	other threads:[~2014-11-27  8:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28  8:55 bug#18577: Regexp I-search: [(error Stack overflow in regexp matcher)] Alan Mackenzie
2014-09-28 10:56 ` Andreas Schwab
2014-09-28 12:37   ` Alan Mackenzie
2014-09-28 12:48     ` Andreas Schwab
2014-09-28 17:35       ` Stefan Monnier
2014-11-27  8:44         ` Tassilo Horn [this message]
2021-10-23  2:47         ` Stefan Kangas
2021-10-23  7:32           ` Eli Zaretskii
2021-10-23  8:30             ` Stefan Kangas
2021-10-23  8:39               ` Eli Zaretskii
2021-10-23  9:32                 ` Stefan Kangas
2021-10-23 11:27                   ` Eli Zaretskii
2021-10-24 22:08                     ` Stefan Kangas

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=878uixm3rf.fsf@thinkpad-t440p.tsdh.org \
    --to=tsdh@gnu.org \
    --cc=18577@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=schwab@linux-m68k.org \
    /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).