The following issue has been UPDATED.
======================================================================
http://austingroupbugs.net/view.php?id=66
======================================================================
Reported By: msbrown
Assigned To: ajosey
======================================================================
Project: 1003.1(2008)/Issue 7
Issue ID: 66
Category: System Interfaces
Type: Clarification Requested
Severity: Comment
Priority: normal
Status: Interpretation Required
Name: Mark Brown
Organization: IBM
User Reference:
Section: sigaction()
Page Number: 1919
Line Number: 61039
Final Accepted Text: http://austingroupbugs.net/view.php?id=66#c123
======================================================================
Date Submitted: 2009-06-26 15:40 MST
Last Modified: 2009-06-26 15:42 MST
======================================================================
Summary: sigaction/signal lists are different
Description:
COMMENT 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.
======================================================================
----------------------------------------------------------------------
(0000123) msbrown (manager) - 2009-06-26 15:41
http://austingroupbugs.net/view.php?id=66#c123
----------------------------------------------------------------------
Target for TC1 (we will need an 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
|