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

Previous Next

Full log

Message #35 received at 9767 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ken Brown <kbrown <at> cornell.edu>
Cc: schwab <at> linux-m68k.org, 9767 <at> debbugs.gnu.org
Subject: Re: bug#9767: 24.0.90; gdb initialization on Cygwin
Date: Sat, 22 Oct 2011 00:15:45 +0200

> Date: Fri, 21 Oct 2011 16:47:52 -0400
> From: Ken Brown <kbrown <at> cornell.edu>
> CC: Andreas Schwab <schwab <at> linux-m68k.org>, 9767 <at> debbugs.gnu.org
> 
> OK, I figured out what's happening, and it is related to SIGALRM after 
> all.  In line 4406 of process.c, wait_reading_process_output reduces the 
> timeout for the select call (under certain circumstances) in an attempt 
> to prevent select from being interrupted by SIGALRM.  This seems to me 
> to be inherently unreliable, and, in particular, it consistently fails 
> on Cygwin.  In other words, the SIGALRM is delivered before select times 
> out, causing select to get interrupted.  So wait_reading_process_output 
> does indeed loop, and select fails every time (except when a key is 
> pressed).

Why does reducing the timeout works on, say, GNU/Linux, but not on
Cygwin?  What is different?  Clock granularity, perhaps?

Previous Next

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