From: npostavs@users.sourceforge.net
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Cheng-An Yang <rhymer123@gmail.com>, 22149@debbugs.gnu.org
Subject: bug#22149: 24.4; gdb stack overflow in regexp matcher
Date: Thu, 30 Jun 2016 23:16:38 -0400 [thread overview]
Message-ID: <87a8i2hwtl.fsf@users.sourceforge.net> (raw)
In-Reply-To: <m2zixgnfeu.fsf@linux-m68k.org> (Andreas Schwab's message of "Sat, 12 Dec 2015 11:13:13 +0100")
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
tags 22149 confirmed
found 22149 25.0.95
retitle 22149 stack overflow in regexp matcher
quit
Andreas Schwab <schwab@linux-m68k.org> writes:
> Cheng-An Yang <rhymer123@gmail.com> writes:
>
>> I am using Emacs GDB Graphical Interface to debug a large C++ project.
>> When I stop at certain functions, it breaks the GDB interface with the
>> error message "Stack overflow in regexp matcher".
>
> I cannot reproduce that error with Emacs 24.5 when evaluating the
> string-match from the backtrace.
I'm able to reproduce with both 24.5 and 25.0.95. Attaching testcase as
el file to avoid ambiguity. Run as
emacs -Q -l bug-22149-regexp-overflow.el
I'm entirely sure why this regexp triggers an overflow, but one that
doesn't trigger overflow, and I think should match the same is:
"\\([~@&]\\)\\(\"\\(?:\\\\\"\\|[^\"]\\)*\"\\)\n"
[-- Attachment #2: testcase to trigger overflow --]
[-- Type: application/emacs-lisp, Size: 16849 bytes --]
next prev parent reply other threads:[~2016-07-01 3:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 6:16 bug#22149: 24.4; gdb stack overflow in regexp matcher Cheng-An Yang
2015-12-12 10:13 ` Andreas Schwab
2016-07-01 3:16 ` npostavs [this message]
2020-03-13 18:58 ` Mattias Engdegård
2020-03-13 19:39 ` Eli Zaretskii
2020-03-13 20:11 ` Mattias Engdegård
2020-03-14 7:58 ` Eli Zaretskii
2020-03-14 9:04 ` Mattias Engdegård
2020-03-14 10:14 ` Eli Zaretskii
2020-03-14 10:43 ` Mattias Engdegård
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=87a8i2hwtl.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=22149@debbugs.gnu.org \
--cc=rhymer123@gmail.com \
--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 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.