delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-developers-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-developers-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin-developers/> |
List-Post: | <mailto:cygwin-developers AT cygwin DOT com> |
List-Help: | <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-developers-owner AT cygwin DOT com |
Delivered-To: | mailing list cygwin-developers AT cygwin DOT com |
Date: | Fri, 22 Nov 2002 23:32:15 -0600 |
From: | Steve O <bub AT io DOT com> |
To: | cygwin-developers AT cygwin DOT com |
Subject: | Re: Want to release 1.3.16 |
Message-ID: | <20021122233215.A15763@fnord.io.com> |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.2.5.1i |
On Thu, 21 Nov 2002, Christopher Faylor wrote: > My "solution" to this problem was just to use large OS pipe buffers for ttys. > That seems to "solve" the problem on NT4 and XP. I didn't try it on any > Windows 9x variant, though. I'm not familiar with how Windows deals with it's buffers, but does that mean that every tty allocates 64K of "kernel" memory? Also, here's a test to try before releasing: in an rxvt, or xterm: cat /bin/cygwin1.dll This hangs for me with the CVS version as of 8pm 20021122 on XP. -steve
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |