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:	Fri, 27 Aug 2004 20:17:09 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: signal delivery problem (with pthreads)
Message-ID:	<20040828001709.GA3261@coe.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20040827181156 DOT GB2008 AT tonfa>
Mime-Version:	1.0
In-Reply-To:	<20040827181156.GB2008@tonfa>
User-Agent:	Mutt/1.4.1i

On Fri, Aug 27, 2004 at 09:11:56PM +0300, Valery A. Frolov wrote:
>In short:
>First signal delivery on call of pthread_kill(tid, SIGUSR1) works fine
>but second one delivers signal with _delay_ and _twice_, and then my
>own daemon crash. This is on cygwin1.dll 1.5.10-3 and snapshot of
>2004-08-21. But on cygwin1.dll 1.5.7-1 all works _fine_ and _long_ time.
>
>In detail:
>(Sorry for my bad English.)
>(And sorry for long letter.)
>(And much more sorry if this is not appropriate place to ask this question.)

Sorry, but if this is really a problem, you're going to have to provide a
simple test case which reproduces it.  Providing a description of the
symptoms is not going to do it and neither is unsolicited strace output.

--
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 -