Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 9 Dec 2003 21:10:51 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Problem with pthreads and signaling, behavior broken...
Message-ID:	<20031210021051.GE5059@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<Law12-F1064IEYMLR6u0002158c AT hotmail DOT com>
Mime-Version:	1.0
In-Reply-To:	<Law12-F1064IEYMLR6u0002158c@hotmail.com>
User-Agent:	Mutt/1.4.1i

On Tue, Dec 09, 2003 at 10:51:48PM +0000, Marcus Van Der Beek wrote:
>i tried the code you provided, it does resolve the issue, however why do
>we need to change the test?

Let me say it again:  I don't see the problem either with my changes or
without it.  I just didn't see any good reason to go on creating threads
after a signal has been received which the original code did.  The usual
effect of hitting CTRL-C is for the program to start shutting down rather
than running at full speed for a while and then eventually dying minutes
later.

My code clearly demonstrates that CTRL-C is being handled.  That's basically
what I care about.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -