From: Ernesto Alfonso <erjoalgo@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 23667@debbugs.gnu.org
Subject: bug#23667: 24.4; "Stack overflow in regexp matcher" happens in only some buffers, for the same arguments
Date: Wed, 1 Jun 2016 07:42:53 -0700 [thread overview]
Message-ID: <CAOckuXDRZyovTksTr7qoJ3YF1Hsz90Vyq0XXjAAW5ZSeH05Baw@mail.gmail.com> (raw)
In-Reply-To: <b97fe94dql.fsf@fencepost.gnu.org>
Hi,
I wasn't aware that [:space:] could vary by buffer. I replaced with
the exact character class I want and I'm no longer getting the stack
overflow.
Feel free to close this report as a mistake on my end. Though ideally
string-match shouldn't crash for that length of input, I could see
easily users working with buffers of that size.
Thanks,
Ernesto
On 5/31/16, Glenn Morris <rgm@gnu.org> wrote:
> Ernesto Alfonso wrote:
>
>> (let ((out (shell-command-to-string "curl
>> http://pastebin.com/raw/a2pMaW6h")))
>> (string-match "\\(^[[:space:]]*\\([a-z]+\\) = \\(.*\\)\n\\)+" out 0))
>>
>> If I try this sexp on an ielm-mode or emacs-lisp-mode buffer (just two
>> examples I tested), this evaluates to 0. If I try it on a message-mode
>> or erc buffer, I get "Stack overflow in regexp matcher".
>
> (length out) = 325969
>
>> The evaluation should be independent of the buffer since no buffer
>> contents should be involved.
>
> [:space:] matches characters with whitespace syntax, and syntax is
> buffer-local and varies between major modes. If you don't want that,
> replace [:space:] with the exact characters you want to match.
>
>
next prev parent reply other threads:[~2016-06-01 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 2:41 bug#23667: 24.4; "Stack overflow in regexp matcher" happens in only some buffers, for the same arguments Ernesto Alfonso
2016-06-01 6:36 ` Glenn Morris
2016-06-01 14:42 ` Ernesto Alfonso [this message]
2016-06-01 17:44 ` Glenn Morris
2016-06-04 8:42 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOckuXDRZyovTksTr7qoJ3YF1Hsz90Vyq0XXjAAW5ZSeH05Baw@mail.gmail.com \
--to=erjoalgo@gmail.com \
--cc=23667@debbugs.gnu.org \
--cc=rgm@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.