Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Feb 2004 09:53:42 -0500 (EST)
From:      Daniel Eischen <eischen@vigrid.com>
To:        David Xu <davidxu@freebsd.org>
Cc:        freebsd-threads@freebsd.org
Subject:   Re: kern/33951: pthread_cancel is ignored
Message-ID:  <Pine.GSO.4.10.10402100950310.15932-100000@pcnet5.pcnet.com>
In-Reply-To: <40287A33.9050008@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Feb 2004, David Xu wrote:

> Daniel Eischen wrote:
> 
> >Synopsis: pthread_cancel is ignored
> >
> >State-Changed-From-To: open->closed
> >State-Changed-By: deischen
> >State-Changed-When: Mon Feb 9 21:30:56 PST 2004
> >State-Changed-Why: 
> >This works under -current with libpthread and supposedly
> >under -stable with -lc_r.
> >
> >http://www.freebsd.org/cgi/query-pr.cgi?pr=33951
> >_______________________________________________
> >freebsd-threads@freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-threads
> >To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org"
> >
> >
> >  
> >
> 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.

-- 
Dan Eischen



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10402100950310.15932-100000>