GNU bug report logs - #9767
24.0.90; gdb initialization on Cygwin

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: kbrown <at> cornell.edu, 9767 <at> debbugs.gnu.org
Subject: bug#9767: 24.0.90; gdb initialization on Cygwin
Date: Thu, 20 Oct 2011 00:02:17 +0200

> From: Andreas Schwab <schwab <at> linux-m68k.org>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  9767 <at> debbugs.gnu.org
> Date: Wed, 19 Oct 2011 23:03:23 +0200
> 
> Ken Brown <kbrown <at> cornell.edu> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.