Hi All,
Attached is a proposed resolution of an interpretation request.
This is on the interpretations track and has a 30 day timer associated.
Please can I have comments back by close of business Friday June 28 2002.
regards
Andrew
_____________________________________________________________________________
Notice: This is an unapproved draft interpretation. Use at
your own risk.
_____________________________________________________________________________
Austin Group Interpretation reference
1003.1-2001 #004
_____________________________________________________________________________
Interpretation Number: XXXX
Topic: Defect in XSH sigaction
Relevant Sections: sigaction
Austin Group Interpretation Request:
------------------------------------
From: yyyyy@xxxxxxxxxx
Date: Tue, 30 Apr 2002 08:58:50 +0100 (BST)
------------------------------------------------------------------------
7 Defect Report concerning (number and title of International Standard
or DIS final text, if applicable):
The System Interfaces Volume of IEEE Std 1003.1-2001
------------------------------------------------------------------------
8 Qualifier (e.g. error, omission, clarification required):
3. Clarification required
------------------------------------------------------------------------
9 References in document (e.g. page, clause, figure, and/or table
numbers):
Page: 1341 Line: 41562 Section: sigaction
XSH Enhancement Request Number 53
------------------------------------------------------------------------
10 Nature of defect (complete, concise explanation of the perceived
problem):
The standard says:
[ENOTSUP]
The SA_SIGINFO flag is set in the sa_flags field of the sigaction
structure, and the implementation does not support either the Realtime
Signals Extension option, or the X/Open System Interfaces Extension
option.
It is not clear if the same errno value should be expected if the
implementation does not support realtime behavior for certain signals
(e.g. if the returning of additional information is provided only for
realtime signals SIGRTMIN..SIGRTMAX).
The relevant quote permitting the implementation to behave in such way
is XBD, pages 301-302 (signal.h), lines 10751-10758:
This header shall also declare macros SIGRTMIN and SIGRTMAX, ... ...
It is implementation-defined whether realtime signal behavior is
supported for other signals.
------------------------------------------------------------------------
11 Solution proposed by the submitter (optional):
Ideally, such situation should be described as a reason for
ENOTSUP/other errno values in the sigaction's description.
------------------------------------------------------------------------
Interpretation response
------------------------
The standard does not speak to this issue, since the ENOTSUP error
addresses the cases when either the Realtime Signals Extension is not supported
or the XSI extension is not supported, and not this case explicitly.
As such no conformance distinction can be made between alternative
implementations based on this.
Thus on systems that do support realtime signals but do not support SA_SIGINFO
on signals not in the range SIGRTMIN..SIGRTMAX (non realtime signals),
ENOTSUP would be an allowable error when SA_SIGINFO is requested on the non
realtime signals.
This is being referred to the sponsor.
Rationale:
-------------
None.
Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
In a future revision, Add a may fail error :
The SA_SIGINFO flag is set in the sa_flags field of the sigaction
structure for a signal not in the range SIGRTMIN..SIGRTMAX
Forwarded to Interpretations Group: 28 May 2002
Proposed resolution: 28 May 2002
-----
Andrew Josey The Open Group
Austin Group Chair Apex Plaza,Forbury Road,
Email: yyyyyyy@xxxxxxxxxxxxx Reading,Berks.RG1 1AX,England
Tel: +44 118 9508311 ext 2250 Fax: +44 118 9500110
|