X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 13 Feb 2008 12:43:23 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: pthread_kill when sig is zero Message-ID: <20080213174323.GA32034@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20080213142351 DOT EB79477A89 AT ems008 DOT s DOT etech DOT sk> <20080213165103 DOT GB15445 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080213165103.GB15445@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, Feb 13, 2008 at 11:51:03AM -0500, Christopher Faylor wrote: >On Wed, Feb 13, 2008 at 03:23:51PM +0100, klement2 wrote: >> >>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 ? > >Yes. I'll fix current CVS. > >Do you happen to have a simple test case which demonstrates this problem? A new snapshot has been generated with the fix: http://cygwin.com/snapshots/ -- 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/