From owner-freebsd-threads@FreeBSD.ORG  Tue Feb 10 16:49:16 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6C95516A4CE
	for <freebsd-threads@freebsd.org>;
	Tue, 10 Feb 2004 16:49:16 -0800 (PST)
Received: from bento.FreeBSD.org (bento.freebsd.org [216.136.204.23])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 682A843D1F; Tue, 10 Feb 2004 16:49:16 -0800 (PST)
	(envelope-from davidxu@freebsd.org)
Received: from freebsd.org (localhost [127.0.0.1])
	by bento.FreeBSD.org (8.12.10/8.12.10) with ESMTP id i1B0nEQt005878;
	Tue, 10 Feb 2004 16:49:15 -0800 (PST)
	(envelope-from davidxu@freebsd.org)
Message-ID: <40297C15.2030407@freebsd.org>
Date: Wed, 11 Feb 2004 08:49:25 +0800
From: David Xu <davidxu@freebsd.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.5b) Gecko/20030723 Thunderbird/0.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Eischen <eischen@vigrid.com>
References: <Pine.GSO.4.10.10402100950310.15932-100000@pcnet5.pcnet.com>
In-Reply-To: <Pine.GSO.4.10.10402100950310.15932-100000@pcnet5.pcnet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: tege@swox.se
cc: freebsd-threads@freebsd.org
Subject: Re: kern/33951: pthread_cancel is ignored
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2004 00:49:16 -0000

Daniel Eischen wrote:

>>I had enabled asynchornous cancelling for M:N thread in libkse but not 
>>1:1 thread,
>>simplest way to support asynchronous cancelling for 1:1 is to use 
>>signal, but it will
>>occupy a signal like Linux's SIGUSR1, another way is to use upcall,  
>>but  it is
>>slight complicated.
>>    
>>
>
>An upcall would be nice since it wouldn' use a signal.  It could
>be treated like a signal where you push it on the thread's stack
>but use the upcall function instead of a signal handling function.
>
>  
>
I am working on it,  hope I can work out a patch in next days.