gwin 1.7.5-1 in certain
cases
References:
[adding bug-grep]
On 04/19/2010 03:19 PM, Matthew Kidd wrote:
> We are seeing grep emit 'grep: writing output' multiple times in
> certain cases where the output of grep is piped to another program.
> Specifically, we see it in the follo
ppear in
out.txt; my guess is that they are being sent to STDERR when they
do occur.
- Matthew Kidd
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
pressed Fedora 11 ISO file. Original size
> 3683829760 bytes, compressed size 3576437027. Works like a charm.
I just tried Cygwin 1.7.2 on a 64-bit Window 7 installation using
ActivePerl 5.10 Build 1007. Like you I do not see a problem on Windows
7. So this issue seem to be confined to 64-bit Window
>> >> I upgraded to Cygwin 1.7.1 on a (64-bit) Windows Server 2003
>> >> and immediately ran into trouble. It seems that Perl can no
>> >> longer shutdown pipes related to Cygwin executables. Here is
>> >> some example code:
>> >>
>> >> #!/usr/bin/perl
>> >>
>> >> use strict;
>> >>
>> >> # my $f
the code above spawns a single gzip.exe child process. But on
64-bit Windows it spawns a gzip process which in turn spawns a gzip
process where the lowest level process is the one that seems to be doing
the work, i.e. is burning CPU. This behavior does not seem unique to the
Cygwin environment but
atter if I use 32-bit or 64-bit Perl.
If I replace the cygwin1.dll file from the 1.7.1 installation with an older
version of cygwin1.dll from a different installation (specifically 1.5.25
cr-0x5f1), the code above works fine (though I imagine mixing and matching
DLL version is not a good long
6 matches
Mail list logo
