Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 27 Oct 2000 11:31:27 -0400 From: Christopher Faylor To: cygwin AT sources DOT redhat DOT com Subject: Re: [patch] ambiguous else Message-ID: <20001027113127.A31974@redhat.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <17B78BDF120BD411B70100500422FC6309E147 AT IIS000> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <17B78BDF120BD411B70100500422FC6309E147@IIS000>; from Dautrevaux@microprocess.com on Fri, Oct 27, 2000 at 02:21:12PM +0200 On Fri, Oct 27, 2000 at 02:21:12PM +0200, Bernard Dautrevaux wrote: >> -----Original Message----- >> From: Jimen Ching [mailto:jching AT flex DOT com] >> Sent: Friday, October 27, 2000 6:53 AM >> To: cygwin AT sourceware DOT cygnus DOT com >> Subject: [patch] ambiguous else >> >> >> Hi all, >> >> Can someone verify that the following patch is needed. >> >> Also, in exceptions.cc, there is a comment in interrupt_setup >> which says >> it is not multi-thread aware. I am running into a strange >> problem where I >> see an error about "couldn't send signal 14" and "wait for >> sig_complete >> event failed, ..." Are these related? Can someone give me >> some hints as >> to where to start looking if I want to know why these >> messages are showing >> up? Thanks. >> >> --jc >> >> -------------------------------------------------------------------- >> diff -u -r1.51 sigproc.cc >> --- sigproc.cc 2000/10/23 20:50:36 1.51 >> +++ sigproc.cc 2000/10/26 03:47:13 >> @@ -1121,10 +1121,12 @@ >> * this thread should terminate. >> */ >> if (rc == WAIT_TIMEOUT) >> + { >> if (!sig_loop_wait) >> break; // Exiting >> else >> continue; >> + } >> >> if (rc == WAIT_FAILED) >> { >> > > >These are not *needed*, but having them avoids anybody to wonder if the code >is doing this or that... The indentation should be a clue here. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com