Date: Mon, 30 Apr 2012 09:12:21 GMT From: Valentin Nechayev <netch@netch.kiev.ua> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/19402: Signals 127 and 128 cannot be detected in wait4() interface Message-ID: <201204300912.q3U9CL9Z049928@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/19402; it has been noted by GNATS. From: Valentin Nechayev <netch@netch.kiev.ua> To: Jilles Tjoelker <jilles@stack.nl> Cc: bug-followup@FreeBSD.org, bde@FreeBSD.org Subject: Re: kern/19402: Signals 127 and 128 cannot be detected in wait4() interface Date: Mon, 30 Apr 2012 12:04:54 +0300 Hi, Mon, Apr 30, 2012 at 00:46:19, jilles wrote about "Re: kern/19402: Signals 127 and 128 cannot be detected in wait4() interface": > > [problems with signals 127 and 128] > > First, note that "clean" programs cannot use signals 127 and 128 because > they do neither have a SIG* constant nor are in the range SIGRTMIN to > SIGRTMAX. You are correct here now, but not at the time I have issued the original request. Values for SIGRTMIN, SIGRTMAX initially appeared only in version 1.47 (Oct 2005) and was incorrect. Revision 1.53 reduced SIGRTMAX from 128 to 126 exactly concerning this my PR. So, if we stick on treating 126 as maximal possible signal number which doesn't break existing ABI, all seems satisfied and I suggest simply to close it as fixed. No need to change any more. -netch-
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204300912.q3U9CL9Z049928>