public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: John Hood <cgull@glup.org>
Subject: Re: cygwin.dll: bug with select on Windows console
Date: Fri, 08 Jan 2016 16:31:00 -0000	[thread overview]
Message-ID: <20160108162906.GJ20447@calimero.vinschen.de> (raw)
In-Reply-To: <568EABDC.1050606@glup.org>

[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]

On Jan  7 13:18, John Hood wrote:
> Sorry about forgetting the testcase (which was good, actually, that
> version had a bug).  I've attached it here.  This takes a single
> argument, the timeout value for select() in microseconds.  A value of
> 1000000 is fine for testing this issue.  Type at it, or just bang on the
> keyboard with random keystrokes, and it will report the results from
> select() and the characters read.  On a Windows console, it should
> report an error within a few seconds.  Moving the mouse cursor over the
> Windows console window while typing seems to provoke the error as well. 

No chance.  I tried this for a good hour now with the unpatched Cygwin
DLL on 32 bit W7 and 64 bit W10 in 32 and 64 bit in a Windows console,
and I can't provoke this error.  It just works for me.

> On mintty or any other pty, the error never occurs.
> 
> I've been unable to build Cygwin from Git on my 32-bit install on Win7,
> thanks to various header mismatches and missing packages-- I think the
> latest was a mingw-gcc header, but I can't check that machine now.  The
> FAQ entry on how to build Cygwin is quite incomplete.  Are there any
> better directions for building Cygwin?

What exactly is failing?  If you installed all the packages mentioned in
the FAQ entry, plus building outside the source tree as outlined, you
should be fine.  Alternatively, install the cygport package and the
2.4.0-0.16 source package and build that via

  cygport cygwin.cygport prep compile

That should get you started.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-01-08 16:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28  1:50 john hood
2016-01-02  2:06 ` John Hood
2016-01-03  0:45   ` Mark Geisert
2016-01-07  0:48 ` Mark Geisert
2016-01-07 17:30 ` Corinna Vinschen
2016-01-07 18:18   ` John Hood
2016-01-07 18:55     ` John Hood
2016-01-08 16:31     ` Corinna Vinschen [this message]
2016-01-08 21:30       ` john hood
2016-01-08 22:21         ` Achim Gratz
2016-01-09 14:41         ` Corinna Vinschen
2016-01-09 14:42           ` Corinna Vinschen
2016-01-10  9:09             ` John Hood
2016-01-11 11:52               ` Corinna Vinschen
2016-01-12 17:32                 ` john hood
2016-01-12 22:09                   ` Corinna Vinschen
2016-01-14 15:22           ` cygwin.dll: bug with select on Windows console / 2.4.0-0.19 Thomas Wolff
2016-01-14 20:24             ` Corinna Vinschen

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=20160108162906.GJ20447@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cgull@glup.org \
    --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).