From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Piping on 64-bit Cygwin, STC found
Date: Tue, 21 Jun 2016 22:55:00 -0000 [thread overview]
Message-ID: <7365C9D7-91DF-491F-A979-A3B7291CFC99@etr-usa.com> (raw)
In-Reply-To: <7E3D11F0-CD6B-4AF4-991B-2C3AD0E08D07@etr-usa.com>
On Jun 21, 2016, at 3:57 PM, Warren Young <wyml@etr-usa.com> wrote:
>
> Here’s what a simple test case looks like:
>
> $ dd if=/dev/urandom bs=4k count=4m |
> gpg -c --force-mdc |
> gpg -d > /dev/null
I seem to have stumbled upon the actual STC. Just increase those values, launch two MinTTY terminals, and try to use Cygwin in the second while the GPG pipeline is running. All will be well for a while, but eventually the second window will start to behave strangely.
I used 64k and 64M (capitalization is important to dd), and the failure I observed is that “man” commands wouldn’t always return you to the shell properly after exiting from the piped-to less process.
Some kind of memory leak, perhaps?
--
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 prev parent reply other threads:[~2016-06-21 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1989991589.1040675.1465521483978.JavaMail.yahoo.ref@mail.yahoo.com>
2016-06-10 1:55 ` [ANNOUNCEMENT] llvm 3.7.1-2 lloyd.wood
2016-06-10 2:58 ` Yaakov Selkowitz
2016-06-21 1:44 ` Jon Turney
2016-06-21 7:48 ` Piping on 64-bit Cygwin was " lloyd.wood
2016-06-21 22:19 ` Warren Young
2016-06-21 22:55 ` Warren Young [this message]
2016-06-21 23:00 ` Piping on 64-bit Cygwin, STC found Warren Young
2016-06-22 3:59 ` Andrey Repin
2016-06-22 12:40 ` Warren Young
[not found] <707580695.12657516.1466595991066.JavaMail.yahoo.ref@mail.yahoo.com>
2016-06-22 14:01 ` lloyd.wood
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=7365C9D7-91DF-491F-A979-A3B7291CFC99@etr-usa.com \
--to=wyml@etr-usa.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).