A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1954 
====================================================================== 
Reported By:                stephane
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1954
Category:                   Shell and Utilities
Type:                       Enhancement Request
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Stephane Chazelas 
Organization:                
User Reference:              
Section:                    trap utility 
Page Number:                2565 
Line Number:                83714-83716 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2025-11-07 20:40 UTC
Last Modified:              2025-11-11 21:33 UTC
====================================================================== 
Summary:                    please allow shells to unignore signals
====================================================================== 

---------------------------------------------------------------------- 
 (0007316) stephane (reporter) - 2025-11-11 21:33
 https://www.austingroupbugs.net/view.php?id=1954#c7316 
---------------------------------------------------------------------- 
Re: https://www.austingroupbugs.net/view.php?id=1954#c7311

>  It's also required behaviour for all standard utilities where ASYNCHRONOUS
EVENTS says "Default" or specifies "the standard action" for a given signal.
(See XCU 1.4 Utility Description Defaults).

Looks like none of GNU grep, GNU awk, or procps ps (among the handful I tried)
are compliant then:

<pre>
$ sh -c 'trap "" SEGV FPE BUS; </proc/self/status exec gawk /Sig...:/'
SigPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000001000
SigCgt: 00000000000004c0
</pre>

It installed handlers on SEGV FPE BUS even though they were ignored on entry.

<pre>
$ sh -c 'trap "" SEGV; </proc/self/status exec grep Sig...:'
SigPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 0000000000000400
</pre>

<pre>
$ sh -c 'trap "" HUP INT ILL TRAP BUS; exec ps --signames -o
ignored,caught,comm'
IGNORED                     CAUGHT                      COMMAND
QUIT,SEGV,USR2,PIPE,TERM+   HUP,INT,ILL,BUS,FPE,SEGV+   zsh
INT                         HUP,INT,QUIT,ILL,TRAP,BUS+  ps
</pre> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2025-11-07 20:40 stephane       New Issue                                    
2025-11-08 08:27 stephane       Note Added: 0007302                          
2025-11-08 08:37 stephane       Note Added: 0007303                          
2025-11-08 11:13 stephane       Note Added: 0007304                          
2025-11-11 10:25 geoffclare     Note Added: 0007311                          
2025-11-11 10:50 geoffclare     Note Added: 0007312                          
2025-11-11 18:06 stephane       Note Added: 0007315                          
2025-11-11 21:33 stephane       Note Added: 0007316                          
======================================================================


  • [1003.1(20... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue 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