Subject: bug#9767: 24.0.90; gdb initialization on Cygwin

From: Eli Zaretskii <[email-masked]>
Date: Thu, 20 Oct 2011 00:02:17 +0200

> From: Andreas Schwab <[email-masked]>
> Cc: Eli Zaretskii <[email-masked]>,  [email-masked]
> Date: Wed, 19 Oct 2011 23:03:23 +0200
> 
> Ken Brown <[email-masked]> writes:
> 
> > No, wait_reading_process_output treats EINTR as though it meant there's no
> > input available.
> 
> Which is correct because an interrupted select does not report anything.
> And then the loop will be restarted to call select again.

Yes, that's what I thought should be happening.  Sorry if that was
unclear.

So the question is still why no input is being reported, although
wait_reading_process_output should loop and call `select' again.