X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
X-Spam-Score:	-1.597
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	pthread_kill when sig is zero
Date:	Wed, 13 Feb 2008 15:23:51 +0100
From:	"klement2" <klement2 AT azet DOT sk>
X-Mailer:	Azet.sk V1.00b (webmail client)
X-Original-IP:	212.5.194.155
MIME-Version:	1.0
Message-Id:	<20080213142351.EB79477A89@ems008.s.etech.sk>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

int pthread_kill(pthread_t thread, int sig);

The posix function pthread_kill (in cygwin) does not perform error
checking when the
argument sig is zero, though it should according to standard.
It means ESRCH is not returned when the thread is not valid (for example
it exited before).

Is it possible to correct this ?

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