public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kaz Kylheku <920-082-4242@kylheku.com>
To: cygwin@cygwin.com
Subject: Re: bash pipe race condition
Date: Wed, 04 Oct 2017 03:39:00 -0000	[thread overview]
Message-ID: <3b4549f8494b5b4062e90eecc1dfc356@mail.kylheku.com> (raw)
In-Reply-To: <33e9d184-03b1-5fa5-4c1a-0cca19571a3a@gmail.com>

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?


--
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

  reply	other threads:[~2017-10-04  3:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03  1:06 Matthew McGIllis
2017-10-03 12:56 ` cyg Simple
2017-10-04  3:39   ` Kaz Kylheku [this message]
2017-10-04 14:42     ` cyg Simple

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3b4549f8494b5b4062e90eecc1dfc356@mail.kylheku.com \
    --to=920-082-4242@kylheku.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).