public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1
Date: Thu, 19 Jan 2017 13:23:00 -0000	[thread overview]
Message-ID: <102fbd64-1bc2-41ee-63d2-932a81124b75@cs.umass.edu> (raw)
In-Reply-To: <58804d14.26149d0a.21734.79aa@mx.google.com>

On 1/19/2017 12:22 AM, Steven Penny wrote:
 > On Tue, 17 Jan 2017 21:45:07, Steven Penny wrote:
 >> I would like to keep this productive; my next step is to try to unpack that
 >> large commit, while also helping Eric to reproduce.
 >
 > I have root caused this. With the new readline, running ./configure creates
 > config.h, as expected. However new version adds this line:
 >
 > #define HAVE_PSELECT 1
 >
 > If you remove this from config.h, then make, the resultant DLL behaves as it did
 > with previous readline. Not sure what is causing this change, I will try to dig
 > into it more.

You probably found it, but here's why they added use of pselect:

"h.  Use pselect(2), if available, to wait for input before calling read(2), so
     a SIGWINCH can interrupt it, since it doesn't interrupt read(2)."

Of course that does not explain why it's not working how we would like ...

Regards - EM

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

  reply	other threads:[~2017-01-19 13:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 16:55 Eric Blake (cygwin)
2017-01-13  5:07 ` Steven Penny
2017-01-13 14:47   ` Eric Blake
2017-01-14  0:23     ` Steven Penny
2017-01-14 21:48       ` Eric Blake
2017-01-15  0:27         ` Steven Penny
2017-01-15 13:23           ` Vince Rice
2017-01-15 14:11             ` cyg Simple
2017-01-15 14:30               ` Steven Penny
2017-01-16 10:32                 ` Yaakov Selkowitz
2017-01-16 12:40                   ` Steven Penny
2017-01-15 22:33         ` Thomas Wolff
2017-01-16  0:45           ` Steven Penny
2017-01-16  0:54             ` Steven Penny
2017-01-17  2:47         ` Steven Penny
2017-01-17  3:32           ` Steven Penny
2017-01-18  0:36             ` Steven Penny
2017-01-18  2:08               ` Eric Blake
2017-01-18  3:55                 ` Steven Penny
2017-01-18  4:09                   ` Doug Henderson
2017-01-18  5:02                     ` Larry Hall (Cygwin)
2017-01-18  5:45                       ` Steven Penny
2017-01-19  5:23                         ` Steven Penny
2017-01-19 13:23                           ` Eliot Moss [this message]
2017-01-19 14:21                             ` Eric Blake
2017-01-19 18:13                               ` Corinna Vinschen
2017-01-19 23:54                                 ` Steven Penny
2017-01-20 13:04                                   ` Corinna Vinschen
2017-01-20 14:51                           ` Eric Blake
2017-01-20 15:00                             ` Eric Blake
2017-01-21  3:57                               ` Steven Penny
2017-01-18  1:46     ` Eric Blake

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=102fbd64-1bc2-41ee-63d2-932a81124b75@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).