Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA24154; Wed, 13 Mar 96 12:36:02 EST
Received: from mail.cs.utexas.edu by MIT.EDU with SMTP
	id AA13370; Wed, 13 Mar 96 12:31:01 EST
Received: from cascade.cs.utexas.edu (grib@cascade.cs.utexas.edu [128.83.120.15]) by mail.cs.utexas.edu (8.7.1/8.7.1) with ESMTP id LAA17157 for <pthreads@mit.edu>; Wed, 13 Mar 1996 11:31:44 -0600 (CST)
From: "William S. Gribble" <grib@cs.utexas.edu>
Received: by cascade.cs.utexas.edu (8.7.1/Client-1.4)
	id LAA22878; Wed, 13 Mar 1996 11:31:43 -0600 (CST)
Date: Wed, 13 Mar 1996 11:31:43 -0600 (CST)
Message-Id: <199603131731.LAA22878@cascade.cs.utexas.edu>
To: pthreads@MIT.EDU
Subject: What's going on with MIT pthreads? 

I have been using the beta4_1 release for quite some time now, and it
generally seems to work OK with my Linux setup, modulo some small
difficulties.  I'm wondering what areas have been identified that need
work, what outstanding bugs other people have run into, and whether
the principal developers are still working on MIT pthreads at all.
If work is still being done, where's it heading? 

Is anyone working on integrating MIT pthreads support into gdb?
Kernel thread support for Linux using clone()?  Getting a newer
version incorporated into Linux libc?  A good c++ binding?  These are
just some things off the top of my head.

The remaining problems I have with the 4_1 release I haven't been able to 
precisely pin down, but they're related to signals.  There are conditions 
where signals just get dropped on the floor.. it happens semi-reliably 
when all threads are blocked on I/O or sleeping.  Have other people 
had this problem? 

Bill Gribble