https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239966

--- Comment #2 from Bertrand Petit <[email protected]> ---
That is indeed clearer however this appears to be inaccurate.

If I correctly understand this syscall, for the SIGEV_THREAD case, according to
POSIX, no signal is queued when the timer fires. Instead
evp->sigev_notify_function is called within the context of "a newly created
thread with thread attributes specified by sigev_notify_attributes." 
sigev_notify_thread_id looks to play no role for this case.

Note: I haven't reviewed the implementation, my comment is only based on the
POSIX specification.

Should we mention that sigev_notify_thread_id is not part of POSIX? Shouldn't
we also mention the SIGEV_NONE case?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to