This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: bash pipe race condition

On 10/3/2017 11:39 PM, Kaz Kylheku wrote:
> On 03.10.2017 05:56, cyg Simple wrote:
>> On 10/2/2017 9:06 PM, Matthew McGIllis wrote:
>>> If I use the same code from bash I get:
>>> $ ./input.exe | ./simple.exe
>>> line1
>>> <—— Hangs indefinitely until you kill it or ctrl-c
>>> Some how if input has a delay between its line output then things
>>> will get hung, if you remove the sleep from the input things work,
>>> add the sleep in it fails.
>>> input.exe is generate from input.vb using: vbc input.vb
> [ ... ]
>> It is a known issue of the PTY emulation between a Cygwin runtime and a
>> Windows runtime enabled app.  It just cannot be fixed.  You're even
>> lucky that it works in the Windows command shell.
> Lucky? Are VB console apps known to have unreliable piping when
> used from the Windows command processor?
>> Either convert
>> simple.vb to simple.c and use Cygwin's gcc to build it or create a
>> Windows runtime version of input.exe.
> Isn't that what "input.exe is generate[d] from input.vb using: vbc
> input.vb"
> is referring to?

Oh, yes, sorry I missed that.  Still an issue with PTY and cannot be
fixed regardless without creating a C program of both.  Straight console
on the stdin and stdout channels might work with the C runtime with MS
runtime but should be Cygwin runtime when using Cygwin.

cyg Simple

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]