Date: Sun, 22 Jul 2001 09:54:00 +0300 From: Valentin Nechayev <netch@segfault.kiev.ua> To: mike@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/19402: Signals 127 and 128 cannot be detected in wait4() interface Message-ID: <20010722095359.Q1014@netch.kiev.ua> In-Reply-To: <200107220410.f6M4ANg22095@freefall.freebsd.org>; from mike@FreeBSD.org on Sat, Jul 21, 2001 at 09:10:23PM -0700 References: <200107220410.f6M4ANg22095@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sat, Jul 21, 2001 at 21:10:23, mike wrote about "Re: kern/19402: Signals 127 and 128 cannot be detected in wait4() interface": > Synopsis: Signals 127 and 128 cannot be detected in wait4() interface > > State-Changed-From-To: open->feedback > State-Changed-By: mike > State-Changed-When: Sat Jul 21 21:09:54 PDT 2001 > State-Changed-Why: > > Does this problem still occur in newer versions of FreeBSD, > such as 4.3-RELEASE? Yes, it still occurs. Nobody changed macros in <sys/wait.h> to resolve this conflict, neither in RELENG_4 nor in HEAD. I can create proposition (in form of patch) how they should be changed (this will use fact that wait4() status is 32 bits, but only low 16 bits are used) but this will be ABI change with incompatibility for signals 64...128 when bit shifts are used and only 128 in expensive variant of multiply/delete. Yet another variant is to exclude signals 127 and 128, this variant AFAIU conflicts with POSIX. Another point view is this problem is most architectural and should be first discussed in -arch or -hackers, not in -bugs, and it (problem) is too complicated to fit in frames of gnats db. But IMO it does _not_ mean the PR should be closed, because problem keeps. /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010722095359.Q1014>