RE: 1.7.10 : output from .NET programs does not get through pipeline

2012-03-27 Thread David Kerrawn
> On Mon, Mar 26, 2012 at 05:00:02PM +0100, David Kerrawn wrote: > >I too have noticed this problem or a variation of it. I've narrowed it > down > >to the change in pipe behavior in snapshot cygwin-src-20111023 > > Are you saying that this is still broken in recent snapshots? A fix > for > this

Re: 1.7.10 : output from .NET programs does not get through pipeline

2012-03-26 Thread Christopher Faylor
On Mon, Mar 26, 2012 at 05:00:02PM +0100, David Kerrawn wrote: >I too have noticed this problem or a variation of it. I've narrowed it down >to the change in pipe behavior in snapshot cygwin-src-20111023 Are you saying that this is still broken in recent snapshots? A fix for this went in on March

Re: 1.7.10 : output from .NET programs does not get through pipeline

2012-03-26 Thread David Kerrawn
I too have noticed this problem or a variation of it. I've narrowed it down to the change in pipe behavior in snapshot cygwin-src-20111023 Specifically in http://cygwin.com/snapshots/winsup-diffs-20111022-20111023 +Note that the write side of the pipe is opened as PIPE_TYPE_MESSAGE. +

Re: 1.7.10 : output from .NET programs does not get through pipeline

2012-03-06 Thread Edgar Ellis
Hi all, I started observing some very strange effects when launching .NET programs from cygwin, after upgrading to version 1.7.10. The example below is using the MSBuild.exe as an example, but I get analogous results with any console program compiled for .NET. One can see that each pipeline work

1.7.10 : output from .NET programs does not get through pipeline

2012-02-23 Thread Ilya Beylin
Hi all, I started observing some very strange effects when launching .NET programs from cygwin, after upgrading to version 1.7.10. The example below is using the MSBuild.exe as an example, but I get analogous results with any console program compiled for .NET. One can see that each pipeline works