This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/10815] [timer_create / SIGEV_THREAD] signalmask of timer_sigev_thread dangerous
- From: "tpiepho at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Tue, 13 Nov 2012 23:44:35 +0000
- Subject: [Bug nptl/10815] [timer_create / SIGEV_THREAD] signalmask of timer_sigev_thread dangerous
- Auto-submitted: auto-generated
- References: <bug-10815-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=10815
Trent Piepho <tpiepho at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tpiepho at gmail dot com
--- Comment #2 from Trent Piepho <tpiepho at gmail dot com> 2012-11-13 23:44:35 UTC ---
(In reply to comment #1)
> The behavior is correct. You're relying on undefined behavior. Just don't do
> it.
This means it's impossible to use sigwait()/sigwaitinfo()/sigtimedwait() in the
same process with a POSIX timer using SIGEV_THREAD.
It would be much more useful if the helper thread had the same signal mask as
the thread that originally called timer_create. That signal mask is already
retrieved when the timer thread is created. If it were simply stored
somewhere, then the helper thread could set its mask to that instead of an
empty set.
--
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.