Date: Tue, 27 Jun 2006 04:12:51 +0200 From: "Timur I. Bakeyev" <timur@gnu.org> To: "FreeBSD gnats submit" <FreeBSD-gnats-submit@FreeBSD.org> Subject: standards/99517: Missing SIGRTMIN and SIGRTMAX signals Message-ID: <1151374371.6337@timur.home.bat.ru> Resent-Message-ID: <200606270220.k5R2KFfG009477@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 99517
>Category: standards
>Synopsis: Missing SIGRTMIN and SIGRTMAX signals
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-standards
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Tue Jun 27 02:20:15 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Timur I. Bakeyev
>Release: FreeBSD 6.1-STABLE i386
>Organization:
>Environment:
System: FreeBSD 6.1-STABLE #0: Tue Jun 20 02:38:12 CEST 2006
root@timur.home.bat.ru:/usr/src/sys/i386/compile/COMMON
>Description:
It was a great surprise to me to find out that signal.h (or, in fact, sys/signal.h) doesn't contain definition of such a basic POSIX signal related constants as SIGRTMIN and SIGRTMAX.
They described for example here: http://en.wikipedia.org/wiki/SIGRTMIN
Moreover it's even mentioned in file itself:
/*
* XXX missing SIGRTMIN, SIGRTMAX.
*/
Absence of this variables makes porting of POSIX-compliant applications harder as well as lowers general POSIX-compliance of FreeBSD.
Actually, signal.h looks quite scary with all that:
/*
* XXX missing SIG_HOLD.
*/
/*
* XXX missing SIGEV_THREAD.
*/
>How-To-Repeat:
less /usr/include/sys/signal.h
>Fix:
It'll be nice if that definitions were added to the signal.h ASAP. I don't see any strong reason not to have them.
With regards,
Timur Bakeyev.
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1151374371.6337>