X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=gBAJykhaDSsQD/xeREqsEfTZWFr5
	K35EQPnH00sD2RTn3g506pY0aU+35NcZo2+hgLUfjQQCGqnI2u4LiJeoKlr6UC0/
	gDDhXKXjdqMj9sXN101qeJGWSnAN9d67SJG8L3LyE+bUrHoB2QXJeJwbgniYOJPt
	UDnVonAQ6gHqSKA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=u0Klz7afm7blgHJd3mhC4++BE1s=; b=js
	Y/NyLNxyfyoOsHirJq8/fmW7OFc28OE8S8aCgXScnsP/mmTjFvyB/c98AQ70xE42
	VPOv+m+uZL5cEWga/0WEr5rasGWVmsIQHbl+aRi/7xV5+QBq6N0gSfsN5jB8iAms
	mBx8NdUQD/q2dKtL6fA2JoPQexQDQm45Q88AgMDpA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=UD:imgur.com, Almost, H*f:sk:7365C9D, H*i:sk:7365C9D
X-HELO: etr-usa.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Piping on 64-bit Cygwin, STC found
From: Warren Young <wyml AT etr-usa DOT com>
In-Reply-To: <7365C9D7-91DF-491F-A979-A3B7291CFC99@etr-usa.com>
Date: Tue, 21 Jun 2016 16:49:49 -0600
Message-Id: <8A9A7CC5-69F6-4D1A-839E-14856F0D5778@etr-usa.com>
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> <7365C9D7-91DF-491F-A979-A3B7291CFC99 AT etr-usa DOT com>
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u5LMoFQE028818

On Jun 21, 2016, at 4:40 PM, Warren Young <wyml AT etr-usa DOT com> wrote:
> 
> On Jun 21, 2016, at 3:57 PM, Warren Young <wyml AT etr-usa DOT 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.

Here’s a screen shot of the error the second MinTTY gives on trying to exit:

  https://imgur.com/5RLi4ie

The “man bash” is the command I tried to give, and the “vi” command never executed, even after closing the first MinTTY window.  The defunct “less” process is of course a child of the “man” process.

> Just increase those values...I used 64k and 64M

To be clear, I mean bs=64k count=64M, for 4 TiB of transfer.  This ran for about half an hour before it started causing problems in the other MinTTY window here.  I didn’t write down the amount transferred at that time, unfortunately, though dd did report it.  Almost certainly many times more than available RAM at any rate.

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