Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA04849; Thu, 18 Jan 96 12:53:36 EST
Received: from dxmint.cern.ch by MIT.EDU with SMTP
	id AA07844; Thu, 18 Jan 96 12:47:04 EST
Received: from hpmoose5.cern.ch by dxmint.cern.ch
	id AA29088; Thu, 18 Jan 1996 18:47:11 +0100
Received: by hpmoose5.cern.ch
	(1.38.193.4/16.2) id AA12346; Thu, 18 Jan 1996 18:47:11 +0100
Date: Thu, 18 Jan 1996 18:47:11 +0100 (MET)
From: "Lassi A. Tuura" <lat@afsmail.cern.ch>
X-Sender: lat@hpmoose5.cern.ch
Reply-To: "Lassi A. Tuura" <Lassi.Tuura@cern.ch>
To: pthreads@MIT.EDU
Subject: Re: pthreads and C++
In-Reply-To: <199601181612.KAA00691@cascade.cs.utexas.edu>
Message-Id: <Pine.HPP.3.91.960118184535.12334B-100000@hpmoose5.cern.ch>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

>  An alternative is to kill the thread with a pthread_kill()
> [signal] and have the signal handler throw an exception; however,
> I believe that threads do not handle signals when they are in a 
> blocked state waiting for i/o, mutex, condition variable, etc. 
> True? 

C++ exceptions are not guaranteed to work from signal handlers.
If you try that, beware that it may not work with every compiler.

//LaT
--
Lassi A. Tuura                           Have you not known?
Lassi.Tuura@cern.ch                      Have you not heard?

