100% of the time.
Best regards,
James Johnston
-Original Message-----
Sent: Monday, March 12, 2012 22:02
Subject: Re: Can't reliably redirect standard output from C# program in
recent Cygwin
On Mon, Mar 12, 2012 at 05:28:17PM -, James Johnston wrote:
>Well, good call. I
On Mon, Mar 12, 2012 at 05:28:17PM -, James Johnston wrote:
>Well, good call. I shouldn't have jumped to conclusions. Both my C++
>and C# examples still fail:
Not really a call. It was obviously different failure. The previous
fix wasn't even pipe related.
But, regardless, Corinna (who ha
of the
C version is that it removes the rest of .NET from the test...
Best regards,
James Johnston
-Original Message-
Sent: Monday, March 12, 2012 14:19
Subject: Re: Can't reliably redirect standard output from C# program in recent
Cygwin
On Mar 12 14:05, James Johnston wrote:
&
On Mon, Mar 12, 2012 at 02:05:13PM -, James Johnston wrote:
>You're partially correct, depending on how you look at it... As I wrote
>earlier, I reproduced it with a straight Win32 program, too - by doing a
>null write that every C# program would do. So I guess it's not specific to
>C#, since
On Mar 12 14:05, James Johnston wrote:
> You're partially correct, depending on how you look at it... As I wrote
> earlier, I reproduced it with a straight Win32 program, too - by doing a
> null write that every C# program would do. So I guess it's not specific to
> C#, since C++ programs can cau
gram would
normally do this activity since the runtime always does the null write - so
in that sense, I guess it is somewhat specific to C#.
Thanks all, good to know it should be fixed. :)
James
-Original Message-
Sent: Sunday, March 11, 2012 01:34
Subject: Re: Can't reliably redirect stand
On Fri, Mar 09, 2012 at 08:52:47PM +0100, Corinna Vinschen wrote:
>On Mar 9 18:47, James Johnston wrote:
>> I can reproduce this:
>>
>> C:\cygwin\bin>perl -e 'print "abc";'
>> abc
>> C:\cygwin\bin>perl -e 'print "abc";' | more
>> abc
>>
>> C:\cygwin\bin>perl -e 'print "abc";' | more
>> abc
>>
>
On Mar 9 18:47, James Johnston wrote:
> I can reproduce this:
>
> C:\cygwin\bin>perl -e 'print "abc";'
> abc
> C:\cygwin\bin>perl -e 'print "abc";' | more
> abc
>
> C:\cygwin\bin>perl -e 'print "abc";' | more
> abc
>
> C:\cygwin\bin>perl -e 'print "abc";' | more
>
> C:\cygwin\bin>perl -e 'prin
09
Subject: Re: Can't reliably redirect standard output from C# program in
recent Cygwin
On 3/9/2012 2:24 AM, Bill Meier wrote:
> I've just noticed what sounds like the same issue:
>
> On Windows 7, in a 'cmd' window (at a 'cmd' prompt) doing the
> followin
C:\cygwin\bin>perl -e 'print "abc";' | more
C:\cygwin\bin>perl -e 'print "abc";' | more
I also noticed that the failures took 1 or 2 seconds to run - a significant
delay. The successful runs completed "instantly".
James
-Original Mess
please to the list, not to me
Original Message
Subject: RE: Can't reliably redirect standard output from C# program in
recent Cygwin
Date: Fri, 9 Mar 2012 15:51:51 -
From: James Johnston
To: 'marco atzeri'
I think this is a regression:
1. Used setup to
On 3/9/2012 2:24 AM, Bill Meier wrote:
I've just noticed what sounds like the same issue:
On Windows 7, in a 'cmd' window (at a 'cmd' prompt) doing the following fails
more often than not:
perl -e 'print "abc";' | \cygwin\bin\more
That is: "abc" does not always display on the screen after
the
I've just noticed what sounds like the same issue:
On Windows 7, in a 'cmd' window (at a 'cmd' prompt) doing the following fails
more often than not:
perl -e 'print "abc";' | \cygwin\bin\more
That is: "abc" does not always display on the screen after
the command is executed.
I note that the p
Actually, the problem can be reproduced as follows from a C++ console
program. The issue is not specific to .NET. It appears that Cygwin croaks
if you give it a null write (writing zero bytes):
#include
int _tmain(int argc, _TCHAR* argv[])
{
char * test = "AB";
DWORD written;
14 matches
Mail list logo
