Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Mon, 16 Aug 1999 13:29:19 -0400 To: cygdev Subject: Re: POSIX threads implementation Message-ID: <19990816132919.A1321@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cygdev References: <37B84786 DOT F8BD9EBF AT col DOT bsf DOT alcatel DOT fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37B84786.F8BD9EBF@col.bsf.alcatel.fr>; from Pascal Vittone on Mon, Aug 16, 1999 at 07:16:54PM +0200 On Mon, Aug 16, 1999 at 07:16:54PM +0200, Pascal Vittone wrote: >I am used to work with Solaris' POSIX threads. I tried to use CYGWIN's >threads but I had a lot of problem. So, I read the code. And I think >there is some problems: when a process receives a signal, all the >threads go out of the blocking calls; an exited thread can be chosen to >process a signal; pthread_sigmask modifies process's signal mask; >signals associated to exceptions are not always processed by the >generating thread; ... That sounds correct. The current signal mechanism is not completely correct in its signal delivery. >Is my analysis correct? Are these problems known? Are some of them >features? Do you provide a description of your thread support >implementation? Is someone currently working on threads >implementation? Should I try to correct myself these problems? No one is working on threads, AFAIK. John Fortin has submitted some patches but I don't know if he is actively working on this. The only information available regarding pthreads is in the winsup directory. -chris