This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: [patch] ambiguous else
- To: cygwin at sources dot redhat dot com
- Subject: Re: [patch] ambiguous else
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Fri, 27 Oct 2000 11:31:27 -0400
- References: <17B78BDF120BD411B70100500422FC6309E147@IIS000>
- Reply-To: cygwin at sources dot redhat dot com
On Fri, Oct 27, 2000 at 02:21:12PM +0200, Bernard Dautrevaux wrote:
>> -----Original Message-----
>> From: Jimen Ching [mailto:jching@flex.com]
>> Sent: Friday, October 27, 2000 6:53 AM
>> To: cygwin@sourceware.cygnus.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@sourceware.cygnus.com