Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA07226; Wed, 13 Mar 96 16:40:21 EST
Received: from mail.cs.utexas.edu by MIT.EDU with SMTP
	id AA09161; Wed, 13 Mar 96 16:37:04 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 PAA28342 for <pthreads@mit.edu>; Wed, 13 Mar 1996 15:37:47 -0600 (CST)
From: "William S. Gribble" <grib@cs.utexas.edu>
Received: by cascade.cs.utexas.edu (8.7.1/Client-1.4)
	id PAA23083; Wed, 13 Mar 1996 15:37:46 -0600 (CST)
Date: Wed, 13 Mar 1996 15:37:46 -0600 (CST)
Message-Id: <199603132137.PAA23083@cascade.cs.utexas.edu>
To: pthreads@MIT.EDU
Subject: pthread_cancel() and c++ destructors

I notice that pthread_cancel() is not in the beta4_1 release of MIT
pthreads.  Since I don't have the POSIX document and I can't test the
routine, maybe someone out there can tell me what happens to local
variables in the canceled thread: are their destructors called?  What
about mutexes that are held by the canceled thread?  (btw, I know about 
using a ``token holder'' or locker class to handle unexpected exits, 
I'm just wondering what happens if they aren't used)

Thanks,
Bill Gribble