[Gc] Re: pthread_cancel(3) confuses 'GC_suspend_all ()'
ludo at gnu.org
Tue Sep 15 00:24:55 PDT 2009
Thanks for the quick reply and detailed analysis!
"Boehm, Hans" <hans.boehm at hp.com> writes:
> Thus I'd be inclined to go ahead and disable cancellation across all
> potential cancellation points we can find, including the one in the
> handler, documenting that one as potentially not completely portable.
> We should also add the warning that Posix asynchronous cancellation
> should never be used with the collector (or, in my opinion, without
It makes sense to me. Glibc’s pthread_setcancelstate(3) shouldn’t
introduce much overhead, so that’s probably OK. Any idea how many
cancellation points lie in libgc code that holds the allocation lock?
More information about the Gc