From: John Hood <cgull@glup.org>
To: cygwin@cygwin.com
Subject: Re: cygwin.dll: bug with select on Windows console
Date: Sat, 02 Jan 2016 02:06:00 -0000 [thread overview]
Message-ID: <568776D4.7020102@glup.org> (raw)
In-Reply-To: <5680953B.8050200@glup.org>
More observations:
* This also happens on a Windows 8.1 VDI install with a different
AV/security solution-- different enough from my machine that I don't
think the Windows/app environment is the cause of this, it looks more
strongly like a Cygwin issue to me.
*
<http://pubs.opengroup.org/onlinepubs/9699919799/functions/pselect.html>
clearly states that select() must zero out all FD_SET bits when it
returns 0.
* Moving the mouse cursor around over the console window (at a bash
prompt, without mouse modes enabled) makes this issue happen *much* more
frequently.
I'd investigate further but on current Git sources, 'make' fails for me
with this:
/home/cgull/src/newlib-cygwin/newlib/libc/configure: line 2164: syntax
error near unexpected token `..'
/home/cgull/src/newlib-cygwin/newlib/libc/configure: line 2164:
`NEWLIB_CONFIGURE(..)'
regards,
--jh
--
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
next prev parent reply other threads:[~2016-01-02 2:06 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 [this message]
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
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=568776D4.7020102@glup.org \
--to=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).