Date: Mon, 19 Aug 2019 13:15:38 +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@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239966 Bug ID: 239966 Summary: timer_create(2): undefined and incorrect symbols mentioned as possible value for the evp->sigev_notify field Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: bugs@FreeBSD.org Reporter: bsdpr@phoe.frmug.org CC: doc@FreeBSD.org In FreeBSD 11.2, the timer_create(2) manpage mentions the SIGEV_SIGNO symbo= l as a possible value for the evp->sigev_notify field. This symbol is not define= d in any of the base headers. I suppose it should had been written as SIGEV_SIGN= AL instead. Likewise, in the same manpage, SIGEV_THREAD_ID is mentioned for the same st= ruct member, however this (defined) symbol refers to kernel threads. I guess that SIGEV_THREAD should had been used instead. For reference, please see /usr/include/sys/signal.h and https://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.htm= l#tag_02_04_02 It looks like the error arose from a confusion between the acceptable value= of the evp->sigev_signo field and the names of the fields these values refer t= o, evp->sigev_signo for the SIGEV_SIGNAL value, and evp->sigev_notify_thread_id for the SIGEV_THREAD value. Since I'm trying for the first time to use that syscall I may be wrong. --=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>