Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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:	Wed, 24 Aug 2005 00:49:55 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com, Samuel Thibault <samuel DOT thibault AT ens-lyon DOT org>
Subject:	Re: threads and signals
Message-ID:	<20050824044955.GC17539@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<20050823205144 DOT GE6716 AT bouh DOT ens-lyon DOT fr>
Mime-Version:	1.0
In-Reply-To:	<20050823205144.GE6716@bouh.ens-lyon.fr>
User-Agent:	Mutt/1.5.8i

On Tue, Aug 23, 2005 at 10:51:44PM +0200, Samuel Thibault wrote:
>The attached program doesn't work as expected: if I run it and try to
>kill it (-15), nothing seem happens.  I if comment out
>pthread_sigmask(), it does work as expected: the handler is called, and
>threads are interrupted.  What's more: if I move pthread_sigmask()
>after the pause() call in the foo() function, killing works twice, but
>no more.

This should be fixed in the latest snapshot.  Or at least, it seems to
now properly emulate linux.

Thanks for the test case.

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 -