GNU bug report logs - #21135
Exception: STATUS_STACK_OVERFLOW at rip=001801C6536

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21135 in the body.
You can then email your comments to 21135 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: AJ Lowell <ajlowell <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: Exception: STATUS_STACK_OVERFLOW at rip=001801C6536
Date: Sun, 26 Jul 2015 11:58:45 -0400

[Message part 1 (text/plain, inline)]

Hello,


version:           grep (GNU grep) 2.21

command line:      grep -A 1 -B 1 -e "build " -E -i -r *

error message:     5718 [main] grep 6880
cygwin_exception::open_stackdumpfile: Dumping stack trace to
grep.exe.stackdump

stack dump:        <see attachment>

root directory:    617098 files, combined size 17721863057B


Directory listing (~20MB compressed) and directory contents (4+ GB
compressed) available if needed.


A.J.

[Message part 2 (text/html, inline)]

[grep.exe.stackdump (application/octet-stream, attachment)]

Message #8 received at 21135 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: AJ Lowell <ajlowell <at> gmail.com>
Cc: 21135 <at> debbugs.gnu.org
Subject: Re: bug#21135: Exception: STATUS_STACK_OVERFLOW at rip=001801C6536
Date: Thu, 30 Jul 2015 14:24:15 -0700

On Sun, Jul 26, 2015 at 8:58 AM, AJ Lowell <ajlowell <at> gmail.com> wrote:
> version:           grep (GNU grep) 2.21
>
> command line:      grep -A 1 -B 1 -e "build " -E -i -r *
>
> error message:     5718 [main] grep 6880
> cygwin_exception::open_stackdumpfile: Dumping stack trace to
> grep.exe.stackdump
>
> stack dump:        <see attachment>
>
> root directory:    617098 files, combined size 17721863057B
>
>
> Directory listing (~20MB compressed) and directory contents (4+ GB
> compressed) available if needed.

Thank you for the report.
A general guideline: when using grep's -r option, there is usually no
need to use "*" to select all (non-hidden) files in a directory.
Instead specify only the directory name (here, "." for current
directory) and no "*", and let grep recursively traverse its
subdirectories. If your use of "*" was intended to expand to a listing
of 617,098 files, I'm not surprised that something went wrong. That
command-line length would typically exceed the maximum allowed on most
systems.

I.e., does the problem still arise with this command?

  grep -A 1 -B 1 -e "build " -E -i -r .

Message #11 received at 21135 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: AJ Lowell <ajlowell <at> gmail.com>, 21135 <at> debbugs.gnu.org
Subject: Re: bug#21135: Exception: STATUS_STACK_OVERFLOW at rip=001801C6536
Date: Sun, 2 Aug 2015 07:20:34 -0700

tags 21135 notabug
close 21135
thanks

On Sun, Aug 2, 2015 at 5:54 AM, AJ Lowell <ajlowell <at> gmail.com> wrote:
> Jim,
>
> I didn't understand -r could be used with a 'literal', not a wildcard.
>
> Your suggestion indeed worked.
>
> Thanks for your help.

Thanks for confirming.
I'm marking this as a non-bug and closing the issue.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.