This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: read bug in Cygwin xterm window only
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin-xfree at cygwin dot com
- Date: Thu, 9 Jun 2005 16:08:16 -0400
- Subject: Re: read bug in Cygwin xterm window only
- References: <20050430005435.71869.qmail@web30206.mail.mud.yahoo.com> <d87g9f$6oj$1@sea.gmane.org>
- Reply-to: cygwin-xfree at cygwin dot com
- Reply-to: cygwin-xfree at cygwin dot com
On Wed, Jun 08, 2005 at 09:22:08PM +0200, Jason Curl wrote:
>On Fri, Apr 29, 2005 at 05:54:35PM -0700, Peter Farley wrote:
>>The following program demonstrates what looks to me
>>like a bug in the "read" function in an xterm (as
>>opposed to a Cygwin console window). To run the test,
>>compile with:
>>
>>gcc -g -o xtermbug.exe xtermbug.c
>>
>>When you run it in a console window, you can enter
>>normal keyboard characters, then a return to see
>>"cmdline=<what you typed>". Press the Esc key to exit
>>the program.
>
>Unfortunately I'm seeing exactly the same problem too, and have so for
>some time. I've also noticed that a read() giving a particular length
>will ignore the length field and actually read more data in some cases.
Peter provided a test case which I used to diagnose a problem with
Cygwin. I fixed the problem and released a new version of cygwin which
fixed the problem so it is unlikely that this is exactly the same
problem.
Please provide a simple test case which shows your specific problem.
And, also please provide the details mentioned at
http://cygwin.com/problems.html .
cgf