This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug nptl/13613] Cancellation is broken in single-threaded processes


http://sourceware.org/bugzilla/show_bug.cgi?id=13613

Siddhesh Poyarekar <siddhesh at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |siddhesh at redhat dot com

--- Comment #2 from Siddhesh Poyarekar <siddhesh at redhat dot com> 2012-05-08 16:45:49 UTC ---
Async cancellation points get activated only when the number of threads are
greater than 1, which is why you're seeing the behaviour you see. What is your
use case anyway? I don't see why something like this should be needed at all.
Of course, I couldn't find anything in the posix definition of pthread_cancel
to not allow something like this:

http://pubs.opengroup.org/onlinepubs/009695399/functions/pthread_cancel.html

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]