From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Vasilij Schneidermann <v.schneidermann@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Regexp matcher stack overflow in org-indent initialization [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.1/lisp/org/)]
Date: Fri, 16 Dec 2016 22:44:34 +0100 [thread overview]
Message-ID: <87d1gr4khp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAPGgwWRXvA4E3Vo=+wCRp7XJWJQkQ88SncrWYgE58U8wbLPSTw@mail.gmail.com> (Vasilij Schneidermann's message of "Fri, 16 Dec 2016 11:34:44 +0100")
Hello,
Vasilij Schneidermann <v.schneidermann@gmail.com> writes:
> I've got a "Stack overflow in regexp matcher" error on startup as I've
> made an Org file my initial buffer. It took me days to reproduce this
> error (by putting `(setq debug-on-error t)` into my init file and
> forgetting about the bug until the error resurfaced), but I've finally
> managed to catch its backtrace:
>
> Debugger entered--Lisp error: (error "Stack overflow in regexp matcher")
> looking-at("[ ]*\\(\\S-+\\)\\(.*[ ]+::\\)?\\([ ]+\\|$\\)")
> org-list-item-body-column(1297)
> org-indent-add-properties(#<marker at 1 in *notes*> 93050 (0 2 0))
> org-indent-initialize-buffer(#<buffer *notes*> (0 2 0))
> org-indent-initialize-agent()
> apply(org-indent-initialize-agent nil)
> timer-event-handler([t 0 0 200000 t org-indent-initialize-agent nil idle 0])
>
> The easiest solution to this would be probably a rewrite of the faulty
> regexp to not backtrack as much. 93050 is `(point-max)` in the file,
> the marker does not point to any buffer and does therefore not have any
> inspectable position.
I slightly simplified the regexp. Does it solve the issue?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-12-16 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 10:34 Bug: Regexp matcher stack overflow in org-indent initialization [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.1/lisp/org/)] Vasilij Schneidermann
2016-12-16 21:44 ` Nicolas Goaziou [this message]
2016-12-18 22:05 ` Vasilij Schneidermann
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=87d1gr4khp.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=v.schneidermann@gmail.com \
/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.