|
From: | Ken Brown |
Subject: | bug#9767: 24.0.90; gdb initialization on Cygwin |
Date: | Wed, 19 Oct 2011 22:11:54 -0400 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 |
On 10/19/2011 6:02 PM, Eli Zaretskii wrote:
From: Andreas Schwab<schwab@linux-m68k.org> Cc: Eli Zaretskii<eliz@gnu.org>, 9767@debbugs.gnu.org Date: Wed, 19 Oct 2011 23:03:23 +0200 Ken Brown<kbrown@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.
You were clear. I was the one who muddied the waters by misreading the code, and Andreas correctly pointed out that I was wrong.
So the question is still why no input is being reported, although wait_reading_process_output should loop and call `select' again.
Yes, that's the question. I'll have to go back to my debugging. Ken
[Prev in Thread] | Current Thread | [Next in Thread] |