Date: Tue, 21 Sep 2021 07:54:11 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239966] timer_create(2): undefined and incorrect symbols mentioned as possible value for the evp->sigev_notify field Message-ID: <bug-239966-227-lEMZ1MK5Ig@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239966-227@https.bugs.freebsd.org/bugzilla/> References: <bug-239966-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239966 --- Comment #2 from Bertrand Petit <bsdpr@phoe.frmug.org> --- That is indeed clearer however this appears to be inaccurate. If I correctly understand this syscall, for the SIGEV_THREAD case, accordin= g 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."=20 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? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239966-227-lEMZ1MK5Ig>