X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
X-Spam-Score: -1.597
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: pthread_kill when sig is zero
Date: Wed, 13 Feb 2008 15:23:51 +0100
From: "klement2" <klement2@azet.sk>
X-Mailer: Azet.sk V1.00b (webmail client)
X-Original-IP: 212.5.194.155
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8";
MIME-Version: 1.0
Message-Id: <20080213142351.EB79477A89@ems008.s.etech.sk>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.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/