From: Matthew McGIllis <matthew@mcgillis.org>
To: cygwin@cygwin.com
Subject: bash pipe race condition
Date: Tue, 03 Oct 2017 01:06:00 -0000 [thread overview]
Message-ID: <B05F4669-BE32-4C5C-B366-555CE37A6761@mcgillis.org> (raw)
Windows 7 Service Pack 1
64-Bit Operating System
Cygwin
$ uname -r
2.9.0(0.318/5/3)
$ uname -m
x86_64
The basic issue is in a normal windows command shell if I do
$ .\input.exe | .\simple.exe
line1
line2
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
input.vb file:
Module input
Sub Main()
Console.Out.WriteLine("line1")
Threading.Thread.Sleep(2000)
Console.Out.WriteLine("line2")
End Sub
End Module
simple.exe is generated from simple.vb using: vbc simple.vb
simple.vb file:
Module simple
Sub Main()
Dim line As String
line = Console.In.ReadLine()
Do Until line Is Nothing
Console.Out.WriteLine(line)
line = Console.In.ReadLine()
Loop
End Sub
End Module
Microsoft (R) Visual Basic Compiler version 11.0.50938.18408
The above problem was found when attempting to use cygwin perl using IPC::Open2 to control stdin and stdout of a VB program. So this may not be a bash specific issue but some sort of generic pipe issue in cygwin.
--
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
next reply other threads:[~2017-10-03 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 1:06 Matthew McGIllis [this message]
2017-10-03 12:56 ` cyg Simple
2017-10-04 3:39 ` Kaz Kylheku
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=B05F4669-BE32-4C5C-B366-555CE37A6761@mcgillis.org \
--to=matthew@mcgillis.org \
--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).