This is the mail archive of the
mailing list for the Cygwin project.
Re: Piping on 64-bit Cygwin, STC found
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Tue, 21 Jun 2016 16:40:18 -0600
- Subject: Re: Piping on 64-bit Cygwin, STC found
- Authentication-results: sourceware.org; auth=none
- References: <1989991589 dot 1040675 dot 1465521483978 dot JavaMail dot yahoo dot ref at mail dot yahoo dot com> <1989991589 dot 1040675 dot 1465521483978 dot JavaMail dot yahoo at mail dot yahoo dot com> <6ecc2a84-449f-01f1-0ef7-440e97a9b850 at dronecode dot org dot uk> <1341561944 dot 11163115 dot 1466484828091 dot JavaMail dot yahoo at mail dot yahoo dot com> <7E3D11F0-CD6B-4AF4-991B-2C3AD0E08D07 at etr-usa dot com>
On Jun 21, 2016, at 3:57 PM, Warren Young <firstname.lastname@example.org> 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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple