From: npostavs@users.sourceforge.net
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: 28329@debbugs.gnu.org
Subject: bug#28329: 25.2; Eshell: 40M+ output: Stack overflow in regexp matcher
Date: Sat, 02 Sep 2017 08:30:01 -0400 [thread overview]
Message-ID: <873785706u.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87lglxbg00.fsf@gmail.com> (Pierre Neidhardt's message of "Sat, 02 Sep 2017 10:34:55 +0100")
Pierre Neidhardt <ambrevar@gmail.com> writes:
> Today I update my Gentoo:
>
> > emerge --update --newuse --deep @world
>
> in Eshell. After a very long output (40M+), the shell started stuttering and hanging, messaging the following errors on every new line of output:
>
> error in process filter: eshell-watch-for-password-prompt: Stack overflow in regexp matcher
> error in process filter: Stack overflow in regexp matcher
>
> The process became so slow it was unlikely it would ever complete, so I terminated it and had to re-run it in a *term*.
Can you get a backtrace if you M-x toggle-debug-on-error? It would be
helpful to get a sample of output which triggers this.
Does changing the password regexp help?
(setq eshell-password-prompt-regexp
(format "^.\\{,80\\}%s.\\{,80\\}:\\s-*\\'"
(regexp-opt password-word-equivalents)))
next prev parent reply other threads:[~2017-09-02 12:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 9:34 bug#28329: 25.2; Eshell: 40M+ output: Stack overflow in regexp matcher Pierre Neidhardt
2017-09-02 12:30 ` npostavs [this message]
2017-09-02 13:27 ` Pierre Neidhardt
2017-09-03 2:19 ` npostavs
2017-09-24 12:55 ` Noam Postavsky
2017-10-21 1:20 ` Noam Postavsky
2017-11-05 13:58 ` Pierre Neidhardt
2017-11-05 14:44 ` Noam Postavsky
2017-11-05 14:54 ` Pierre Neidhardt
2019-06-30 4:58 ` Stefan Kangas
2019-06-30 5:59 ` Pierre Neidhardt
2019-06-30 7:07 ` Stefan Kangas
2019-06-30 13:45 ` Noam Postavsky
2019-06-30 14:48 ` 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
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=873785706u.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=28329@debbugs.gnu.org \
--cc=ambrevar@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 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).