The following issue has been SUBMITTED. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1901 
====================================================================== 
Reported By:                dancross
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1901
Category:                   System Interfaces
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Dan Cross 
Organization:                
User Reference:              
Section:                    sigaction 
Page Number:                2046 
Line Number:                67134-67135 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2025-01-09 16:43 UTC
Last Modified:              2025-01-09 16:43 UTC
====================================================================== 
Summary:                    sigaction() incorrectly states (sig)longjmp are not
in the list of async-signal-safe functions
Description: 
The description of sigaction() currently reads, in part,

"Note that longjmp() and siglongjmp() are not in the list of
async-signal-safe functions."

However, XSH 2.4.3 includes both longjmp() and siglongjmp() in the list of
async-signal-safe functions (page 519, lines 18385 and 18367,
respectively).  Moreover, the description of longjmp() on page 1372 line
46093 explicitly states that longjmp is async-signal-safe; the paragraph
started on that line goes on to discuss caveats around its use in signal
handlers. Presumably this applies to siglongjmp() as well, as it is
described as being equivalent to longjmp() in all respects other than those
specifically documented in its description.
Desired Action: 
The text in sigaction() should be updated to reflect that longmp() and
siglongjmp() are both async-signal-safe, but must be used with caution when
called from a signal handler.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2025-01-09 16:43 dancross       New Issue                                    
2025-01-09 16:43 dancross       Name                      => Dan Cross       
2025-01-09 16:43 dancross       Section                   => sigaction       
2025-01-09 16:43 dancross       Page Number               => 2046            
2025-01-09 16:43 dancross       Line Number               => 67134-67135     
======================================================================


  • [1003.1(20... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group

Reply via email to