View Issue Details

IDProjectCategoryView StatusLast Update
00000661003.1(2008)/Issue 7System Interfacespublic2013-04-16 13:06
Reportermsbrown Assigned Toajosey  
PrioritynormalSeverityCommentTypeClarification Requested
Status ClosedResolutionAccepted As Marked 
NameMark Brown
OrganizationIBM
User Reference
Sectionsigaction()
Page Number1919
Line Number61039
Interp StatusApproved
Final Accepted Text0000066:0000123
Summary0000066: sigaction/signal lists are different
DescriptionCOMMENT Enhancement Request Number 4
 tydeman:xxxxxxxxx Bug in XSHd5.1 sigaction() (rdvk# 6)
 {sigaction-signal} Thu, 24 Jul 2008 17:15:56 +0100 (BST)
 _____________________________________________________________________________

sigaction() at line 61039 lists abort(), kill(), raise(). While
 signal() at line 61636 lists abort(), raise(), kill(), pthread_killl(),
 and sigqueue(). Seems strange to have a different list of functions.
Desired Action Review the list of exceptional functions for signal() and sigaction()
 to make sure they should be different.
Tagstc1-2008

Relationships

has duplicate 0000194 Closedajosey 1003.1(2008)/Issue 7 environ use not mentioned as async-unsafe 
related to 0001905 Resolved 1003.1(2024)/Issue8 Conflicting text about async-signal-safety 

Activities

msbrown

2009-06-26 15:41

manager   bugnote:0000123

Last edited: 2009-10-09 16:31

Interpretation response
------------------------
The standard states the requirements for sigaction and signals
and conforming implementations must conform to this. However, concerns
have been raised about this which are being referred to the sponsor."

Rationale:
-------------
None.

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------

On signal() D5.1R pg 1937 61636 replace the para with
    [CX]If the process is multithreaded[/CX], or if the process is
    single threaded and a signal handler is executed other than as
    the result of:

       * the process calling abort(), raise(), [CX]kill(),
         pthread_kill(), or sigqueue()[/CX] to generate a signal
         that is not blocked, or

       * [CX]a pending signal being unblocked and being delivered
         before the call that unblocked it returns[/CX]

    the behavior is undefined if the signal handler refers to any
    object [CX]other than errno[/CX] with static storage duration
    other than by assigning a value to an object declared as volatile
    sig_atomic_t, or if the signal handler calls any function defined
    in this standard other than [CX]one of the functions listed in
    Section 2.4 (on page xxx)[/CX].


Also copy the above to 2.4.3 without CX shading
Replacing 16719-16721
"When signal-catching functions are invoked asynchronously with process
execution, the behavior of some of the functions defined by this volume
of POSIX.1-200x is unspecified if they are called from a signal-catching
function."

and change the last piece of the new replacement to
    in this standard other than one of the functions listed
    in the following table:

also delete the paragraph in APP USAGE On sigaction Page: 1919 Line: 61039


(Target for TC1)

Issue History

Date Modified Username Field Change
2009-06-26 15:40 msbrown New Issue
2009-06-26 15:40 msbrown Status New => Under Review
2009-06-26 15:40 msbrown Assigned To => ajosey
2009-06-26 15:40 msbrown Name => Mark Brown
2009-06-26 15:40 msbrown Organization => IBM
2009-06-26 15:40 msbrown Section => sigaction()
2009-06-26 15:40 msbrown Page Number => 1919
2009-06-26 15:40 msbrown Line Number => 61039
2009-06-26 15:41 msbrown Note Added: 0000123
2009-06-26 15:41 msbrown Status Under Review => Interpretation Required
2009-06-26 15:41 msbrown Resolution Open => Accepted As Marked
2009-06-26 15:42 msbrown Final Accepted Text => 0000066:0000123
2009-08-11 16:28 Don Cragun Interp Status => Pending
2009-09-17 15:20 ajosey Note Edited: 0000123
2009-09-17 15:22 ajosey Note Edited: 0000123
2009-09-17 15:41 nick Interp Status Pending => Proposed
2009-10-09 16:31 ajosey Note Edited: 0000123
2009-10-09 16:31 ajosey Interp Status Proposed => Approved
2009-12-10 17:17 msbrown Relationship added has duplicate 0000194
2010-09-20 09:10 geoffclare Tag Attached: tc1-2008
2013-04-16 13:06 ajosey Status Interpretation Required => Closed
2025-02-06 14:40 geoffclare Relationship added related to 0001905