Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <37691FBE.4DBDBB9B@refinity.com>
Date: Thu, 17 Jun 1999 09:18:06 -0700
From: "J. Kleckner" <jeknews1 AT refinity DOT com>
X-Mailer: Mozilla 4.6 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Alain Magloire <alainm AT rcsm DOT ece DOT mcgill DOT ca>
CC: "J. Kleckner" <jeknews1 AT refinity DOT com>, gnu-utils-bug AT gnu DOT org,
        cygwin AT sourceware DOT cygnus DOT com
Subject: Re: cygwin B20.1 xargs grep results in stack fault in kernel32.dll
References: <199906161742 DOT NAA08037 AT mccoy2 DOT ECE DOT McGill DOT CA>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Alain Magloire wrote:
> 
> Bonjour M. J. Kleckner
> 
> > I often get a stack fault running xargs on Win98.  e.g.
> >   xargs grep -i pattern < files.txt
> > where files.txt contains quoted lines as in:
> >
> > "dir/file1"
> > "dir/file2"
> >
> > Seems to be related to the number of files and size of
> > the list file.  Cutting down the max chars per command
> > line with something like
> >   xargs -s 2000 grep -i pattern < files.txt
> > seems to work.  Is there a smaller default for xargs that
> > would make sense for Win32?
> >
> > Empirically, 9058 was the largest that would work on
> > my machine.
> >
> > Comments?
> 
> None.  I don't think this is related to grep, Have you try
> contacting the cygwin folks or DJGPP.

I have not communicated other than with this posting.
I am now copying that email list with this information.
I have checked the FAQ and email archives.  There does not
appear to be a posting quite like this one and certainly
not one with a workaround of limiting the size of the
buffer to make it work.

I agree with you that the problem is not with grep.
The evidence of the buffer size effect suggests that it
is an xargs/Win interaction problem.  Hopefully, this
detailed info can quickly reveal the failure scenario
for someone with a full build/debug environment.

Jim

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com