Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning:	atacama.four-d.de: mail set sender to <tpfaff AT gmx DOT net> using -f
Message-ID:	<3EBF5FF8.6000106@gmx.net>
Date:	Mon, 12 May 2003 10:48:56 +0200
From:	Thomas Pfaff <tpfaff AT gmx DOT net>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	cygwin <cygwin AT cygwin DOT com>
Subject:	Re: pthread_signal() references illegal memory address
References:	<Pine DOT GSO DOT 4 DOT 44 DOT 0305112053330 DOT 393-100000 AT slinky DOT cs DOT nyu DOT edu> <1052726662 DOT 1644 DOT 19 DOT camel AT rufus>
In-Reply-To:	<1052726662.1644.19.camel@rufus>

Kern Sibbald wrote:
> 
> By the way, if it wasn't clear, the problem *is* with the pthread_kill()
> statement. When it is in the program, the program dies. When I remove
> it, the program works (I mean the real program running as a service).
> That was the last thing that I added, so it isn't a question of the 
> culprit being elsewhere.
> 

pthread_kill is broken and has never worked as expected. To fix it the 
signal code in cygwin must be changed to support multithreaded apps, so 
do not expect that this will work in the near future.

Thomas


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