From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: David Bremner <david@tethera.net>,
Marcin Borkowski <mbork@mbork.pl>,
21160@debbugs.gnu.org
Subject: bug#21160: 24.5; message-goto-body crashes with moderately large headers
Date: Thu, 26 Jan 2017 15:21:49 -0500 [thread overview]
Message-ID: <CAM-tV-8bcppG7dfdS+5G9+qgyeX2zWxhrMzqDG-m9iRgeE0EOQ@mail.gmail.com> (raw)
In-Reply-To: <874m0lmw9t.fsf@gnus.org>
retitle 21160 message-goto-body overflows regex stack with large headers
quit
On Thu, Jan 26, 2017 at 2:55 PM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Marcin Borkowski <mbork@mbork.pl> writes:
>
>> On 2015-07-30, at 17:06, David Bremner <david@tethera.net> wrote:
>>
>>> This bug originally arose using message-mode to forward a message with
>>> mml markup "type=message/rfc822 disposition=inline"
>>>
>>> Unfortunately I don't have permission to share the test message, but
>>> the failure of the corresponding line in message-goto-body can be
>>> duplicated as follows.
>>>
>>> 1) start emacs -Q
>>> 2) visit the attached file
>>> 3) run M-: (search-forward-regexp "[^:]+:\\([^\n]\\|\n[ \t]\\)+\n\n" nil t)
>>
>> Confirmed on GNU Emacs 25.1.50.9 (commit fafdfcb). The error message is
>> "Stack overflow in regexp matcher".
>
> I'm unable to reproduce this bug on the current Emacs trunk. It seems
> to do the right thing here...
>
The regex stack limit is greatly increased (*16, I think) on master.
Might still trigger with a larger text.
next prev parent reply other threads:[~2017-01-26 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 15:06 bug#21160: 24.5; message-goto-body crashes with moderately large headers David Bremner
2016-05-04 7:32 ` Marcin Borkowski
2016-05-04 8:24 ` Andreas Schwab
2017-01-26 19:52 ` Lars Ingebrigtsen
2016-05-04 15:05 ` Eli Zaretskii
2016-05-04 20:02 ` Marcin Borkowski
2017-01-26 19:55 ` Lars Ingebrigtsen
2017-01-26 20:21 ` Noam Postavsky [this message]
2017-01-26 20:25 ` Lars Ingebrigtsen
2017-01-26 20:12 ` Lars Ingebrigtsen
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=CAM-tV-8bcppG7dfdS+5G9+qgyeX2zWxhrMzqDG-m9iRgeE0EOQ@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=21160@debbugs.gnu.org \
--cc=david@tethera.net \
--cc=larsi@gnus.org \
--cc=mbork@mbork.pl \
/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.