unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: 28329@debbugs.gnu.org
Cc: Pierre Neidhardt <ambrevar@gmail.com>
Subject: bug#28329: 25.2; Eshell: 40M+ output: Stack overflow in regexp matcher
Date: Fri, 20 Oct 2017 21:20:06 -0400	[thread overview]
Message-ID: <87o9p1e1q1.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87r2uwmf25.fsf@users.sourceforge.net> (Noam Postavsky's message of "Sun, 24 Sep 2017 08:55:30 -0400")

tags 28329 + moreinfo unreproducible
quit

Noam Postavsky <npostavs@users.sourceforge.net> writes:

>> Apparently, the line is just plain too long...
>> I guess limiting the regexp matcher over, say, the first 256 characters
>> would fix the issue.
>> ----------
>
> Can you catch that build output in a file, so it could be reproduced by
> running 'cat build.log' in eshell?  I tried copying the fragment you
> have in your backtrace a couple of times to make it longer, but I was
> unable to trigger the error.  Perhaps the particular contents of the
> string matters too (some values might let the matcher short-circuit the
> backtracking).

ping?





  reply	other threads:[~2017-10-21  1:20 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
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 [this message]
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=87o9p1e1q1.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).