This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/14744] kill -32 $pid or kill -33 $pid on a process cancels a random thread
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Sun, 12 Jan 2014 18:34:40 +0000
- Subject: [Bug nptl/14744] kill -32 $pid or kill -33 $pid on a process cancels a random thread
- Auto-submitted: auto-generated
- References: <bug-14744-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14744
--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Carlos O'Donell from comment #3)
> However the implementation comment seems to indicate desiring support for
> cancellation from another process?
>
> /* We are canceled now. When canceled by another thread this flag
> is already set but if the signal is directly send (internally or
> from another process) is has to be done here. */
> int newval = oldval | CANCELING_BITMASK | CANCELED_BITMASK;
>
> I can't imagine under what use case you would support cancelling a thread in
> a process from another process?
The worrisome bit is the "internally" part which seems to indicate there is
some path inside glibc which can't set the target thread's cancellation status
to "cancelling" which would make it impossible to determine if you should or
should not act on the SIGCANCEL signal (assuming AC-enabled).
--
You are receiving this mail because:
You are on the CC list for the bug.