[1003.1(2013)/Issue7+TC1 0000906]: Ambiguity of abort() behavior racing with sigaction

[Austin Group Bug Tracker via austin-group-l at The Open Group]

A NOTE has been added to this issue. 
== 
https://austingroupbugs.net/view.php?id=906 
== 
Reported By:dalias
Assigned To:
== 
Project:1003.1(2013)/Issue7+TC1
Issue ID:   906
Category:   System Interfaces
Type:   Clarification Requested
Severity:   Editorial
Priority:   normal
Status: New
Name:   Rich Felker 
Organization:   musl libc 
User Reference:  
Section:abort 
Page Number:560 
Line Number:19406-19414 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2014-12-18 02:10 UTC
Last Modified:  2022-06-17 14:22 UTC
== 
Summary:Ambiguity of abort() behavior racing with sigaction
== 

-- 
 (0005851) geoffclare (manager) - 2022-06-17 14:22
 https://austingroupbugs.net/view.php?id=906#c5851 
-- 
Suggested changes...

Page and line numbers are for the 2018 edition.

On page 565 line 19766 section abort(), change:unless the
signal SIGABRT is being caught and the signal handler does not
return.to:unless a SIGABRT signal that it
generates is caught and the signal handler does not return.
On page 565 line 19771 section abort(), change:The SIGABRT
signal shall be sent to the calling process as if by means of
raise() with the argument SIGABRT.to:The
SIGABRT signal shall be sent to the calling [CX]thread[/CX] as if by means
of raise() with the argument SIGABRT. [CX]If this signal does not
terminate the process (for example, if the signal is caught and the handler
returns), abort() may change the disposition of SIGABRT to SIG_DFL
and send the signal (in the same way) again. If a second signal is sent and
it does not terminate the process, the behavior is unspecified, except that
the abort() call shall not return.[/CX]
On page 565 line 19785 section abort(), insert at the start of
RATIONALE:Historically, abort() has been implemented by
calling other signal manipulation functions such as raise(),
sigaction(), and pthread_sigmask(). This means that its
operation can be affected by concurrent actions in other threads. For
example, if abort() attempts to terminate the process by calling
sigaction() to change the disposition for SIGABRT to SIG_DFL and
then calling raise(), another thread could change the disposition in
between those two calls, resulting in the process not being terminated. If
this happens, the only requirement is that abort() does not return.
An implementation could call those functions in a loop (which could in
theory then execute indefinitely), or could terminate the process by
calling _exit() (which would ensure termination but result in the
wrong wait status). To avoid these issues, implementations are encouraged
to implement abort() in a manner such that its operation cannot be
affected by concurrent actions in other threads. For example, it could
first halt the execution of all other threads, or it could terminate the
process using a ``terminate as if by a signal'' system call instead of by
raising (a second) SIGABRT.
On page 566 line 19805 section abort(), change FUTURE DIRECTIONS
from:None.to:A future version of this
standard may require abort to be implemented in a manner such that
its operation cannot be affected by concurrent actions in other
threads. 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2014-12-18 02:10 dalias New Issue
2014-12-18 02:10 dalias Name  => Rich Felker 
2014-12-18 02:10 dalias Organization  => musl libc   
2014-12-18 02:10 dalias Section   => abort   
2014-12-18 02:10 dalias Page Number   => unknown 
2014-12-18 02:10 dalias Line Number   => unknown 
2015-03-26 15:38 Don Cragun Note Added: 0002607  
2015-03-26 15:41 Don Cragun Page Number  unknown => 560  
2015-03-26 15:41 Don Cragun Line Number  unknown => 19406-19414
2015-03-26 15:41 Don Cragun Interp Status => --- 
2022-05-12 15:29 geoffclare Tag Attached: c99

[1003.1(2013)/Issue7+TC1 0000922]: Implementations should be allowed to change/remove implementation-defined environment variables

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=922 
== 
Reported By:Florian Weimer
Assigned To:
== 
Project:1003.1(2013)/Issue7+TC1
Issue ID:   922
Category:   System Interfaces
Type:   Clarification Requested
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Florian Weimer 
Organization:   Red Hat 
User Reference:  
Section:8.1 Environment Variable Definition 
Page Number:   
http://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html 
Line Number:141 
Interp Status:  --- 
Final Accepted Text:https://austingroupbugs.net/view.php?id=922#c5844 
Resolution: Accepted As Marked
Fixed in Version:   
== 
Date Submitted: 2015-02-11 10:08 UTC
Last Modified:  2022-06-17 08:52 UTC
== 
Summary:Implementations should be allowed to change/remove
implementation-defined environment variables
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-02-11 10:08 Florian Weimer New Issue
2015-02-11 10:08 Florian Weimer Name  => Florian Weimer  
2015-02-11 10:08 Florian Weimer Organization  => Red Hat 
2015-02-11 10:08 Florian Weimer Section   => 8.1 Environment
Variable Definition
2015-02-11 10:08 Florian Weimer Page Number   =>
http://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html
2015-02-11 10:08 Florian Weimer Line Number   => 141 
2015-02-11 10:08 Florian Weimer Issue Monitored: Florian Weimer 
  
2015-02-13 18:45 dalias Note Added: 0002546  
2015-04-30 15:39 eblake Note Added: 0002643  
2015-04-30 16:10 eblake Note Added: 0002644  
2015-09-04 18:15 philip-guentherNote Added: 0002810  
2015-09-04 18:34 dalias Note Added: 0002811  
2022-05-26 15:17 geoffclare Note Added: 0005844  
2022-05-26 15:18 geoffclare Interp Status => --- 
2022-05-26 15:18 geoffclare Final Accepted Text   =>
https://austingroupbugs.net/view.php?id=922#c5844
2022-05-26 15:18 geoffclare Status   New => Resolved 
2022-05-26 15:18 geoffclare Resolution   Open => Accepted As
Marked
2022-05-26 15:18 geoffclare Tag Attached: issue8 
2022-05-26 15:19 geoffclare Note Edited: 0005844 
2022-05-26 15:20 geoffclare Note Edited: 0005844 
2022-06-17 08:52 geoffclare Status   Resolved => Applied 
==

[Issue 8 drafts 0001583]: tidy up definition of the term "Special Built-In"

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1583 
== 
Reported By:calestyo
Assigned To:
== 
Project:Issue 8 drafts
Issue ID:   1583
Category:   Base Definitions and Headers
Type:   Enhancement Request
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Christoph Anton Mitterer 
Organization:
User Reference:  
Section:3.335 Special Built-In 
Page Number:76 
Line Number:2335 
Final Accepted Text: 
Resolution: Accepted
Fixed in Version:   
== 
Date Submitted: 2022-05-09 01:13 UTC
Last Modified:  2022-06-17 08:41 UTC
== 
Summary:tidy up definition of the term "Special Built-In"
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2022-05-09 01:13 calestyo   New Issue
2022-05-09 01:13 calestyo   Name  => Christoph Anton
Mitterer
2022-05-09 01:13 calestyo   Section   => 3.335 Special
Built-In
2022-05-09 01:13 calestyo   Page Number   => 76  
2022-05-09 01:13 calestyo   Line Number   => 2335
2022-05-12 15:06 Don Cragun Status   New => Resolved 
2022-05-12 15:06 Don Cragun Resolution   Open => Accepted
2022-05-12 15:06 Don Cragun Tag Attached: tc3-2008   
2022-06-17 08:41 geoffclare Status   Resolved => Applied 
==

[1003.1(2016/18)/Issue7+TC2 0001582]: Algorithm for computing addresses for "address chains" is not clearly specified

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1582 
== 
Reported By:nmeum
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1582
Category:   Shell and Utilities
Type:   Clarification Requested
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Sören Tempel 
Organization:
User Reference:  
Section:ed 
Page Number:2691 
Line Number:87831 
Interp Status:  Approved 
Final Accepted Text:https://austingroupbugs.net/view.php?id=1582#c5829 
Resolution: Accepted As Marked
Fixed in Version:   
== 
Date Submitted: 2022-04-30 10:23 UTC
Last Modified:  2022-06-17 08:39 UTC
== 
Summary:Algorithm for computing addresses for "address
chains" is not clearly specified
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2022-04-30 10:23 nmeum  New Issue
2022-04-30 10:23 nmeum  Name  => Sören Tempel   
2022-04-30 10:23 nmeum  Section   => ed  
2022-04-30 10:23 nmeum  Page Number   => 2691
2022-04-30 10:23 nmeum  Line Number   => 87831   
2022-05-05 16:29 geoffclare Note Added: 0005829  
2022-05-05 16:29 geoffclare Interp Status => Pending 
2022-05-05 16:29 geoffclare Final Accepted Text   =>
https://austingroupbugs.net/view.php?id=1582#c5829
2022-05-05 16:29 geoffclare Status   New => Interpretation
Required
2022-05-05 16:29 geoffclare Resolution   Open => Accepted As
Marked
2022-05-05 16:30 geoffclare Tag Attached: tc3-2008   
2022-05-06 13:21 agadminInterp StatusPending => Proposed 
2022-05-06 13:21 agadminNote Added: 0005830  
2022-06-07 09:27 agadminInterp StatusProposed => Approved
2022-06-07 09:27 agadminNote Added: 0005846  
2022-06-17 08:39 geoffclare Status   Interpretation Required
=> Applied
==

[1003.1(2016/18)/Issue7+TC2 0001563]: Wording for what seem to imply odd behavior. "all occurrences of @(#)"

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1563 
== 
Reported By:andras_farkas
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1563
Category:   Shell and Utilities
Type:   Clarification Requested
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Andras Farkas 
Organization:
User Reference:  
Section:what 
Page Number: 
Line Number: 
Interp Status:  Approved 
Final Accepted Text:https://austingroupbugs.net/view.php?id=1563#c5800 
Resolution: Accepted As Marked
Fixed in Version:   
== 
Date Submitted: 2022-02-18 15:07 UTC
Last Modified:  2022-06-17 08:37 UTC
== 
Summary:Wording for what seem to imply odd behavior. "all
occurrences of @(#)"
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2022-02-18 15:07 andras_farkas  New Issue
2022-02-18 15:07 andras_farkas  Name  => Andras Farkas   
2022-02-18 15:07 andras_farkas  Section   => what
2022-02-18 15:23 andras_farkas  Note Added: 0005684  
2022-02-18 16:02 shware_systems Note Added: 0005686  
2022-02-18 16:17 shware_systems Note Edited: 0005686 
2022-02-18 19:40 kreNote Added: 0005689  
2022-02-21 12:09 geoffclare Note Added: 0005697  
2022-02-21 18:18 andras_farkas  Note Added: 0005698  
2022-04-14 16:34 geoffclare Note Added: 0005800  
2022-04-14 16:35 geoffclare Note Edited: 0005800 
2022-04-14 16:36 geoffclare Interp Status => Pending 
2022-04-14 16:36 geoffclare Final Accepted Text   =>
https://austingroupbugs.net/view.php?id=1563#c5800
2022-04-14 16:36 geoffclare Status   New => Interpretation
Required
2022-04-14 16:36 geoffclare Resolution   Open => Accepted As
Marked
2022-04-14 16:36 geoffclare Tag Attached: tc3-2008   
2022-04-14 19:39 andras_farkas  Note Added: 0005801  
2022-04-21 15:06 agadminInterp StatusPending => Proposed 
2022-04-21 15:06 agadminNote Added: 0005811  
2022-05-23 11:26 agadminInterp StatusProposed => Approved
2022-05-23 11:26 agadminNote Added: 0005842  
2022-06-17 08:37 geoffclare Status   Interpretation Required
=> Applied
==

[1003.1(2016/18)/Issue7+TC2 0001555]: -a/allexport spec should cover ${var=value} and ${var:=value}

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1555 
== 
Reported By:McDutchie
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1555
Category:   Shell and Utilities
Type:   Clarification Requested
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Martijn Dekker 
Organization:   ksh 93u+m  
User Reference:  
Section:XCU 2.14 
Page Number:2381 
Line Number:77125-77127 
Interp Status:  Approved 
Final Accepted Text:https://austingroupbugs.net/view.php?id=1555#c5769 
Resolution: Accepted As Marked
Fixed in Version:   
== 
Date Submitted: 2022-01-17 22:32 UTC
Last Modified:  2022-06-17 08:34 UTC
== 
Summary:-a/allexport spec should cover ${var=value} and
${var:=value}
==
Relationships   ID  Summary
--
related to  0001009 remain in affect after and ...
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2022-01-17 22:32 McDutchie  New Issue
2022-01-17 22:32 McDutchie  Name  => Martijn Dekker  
2022-01-17 22:32 McDutchie  Organization  => ksh 93u+m

2022-01-17 22:32 McDutchie  Section   => XCU 2.14
2022-01-17 22:32 McDutchie  Page Number   => 2381
2022-01-17 22:32 McDutchie  Line Number   => 77125-77127 
2022-01-19 02:35 McDutchie  Note Added: 0005628  
2022-03-31 15:52 nick   Relationship added   related to 0001009  
2022-03-31 15:56 geoffclare Interp Status => Pending 
2022-03-31 15:56 geoffclare Note Added: 0005769  
2022-03-31 15:56 geoffclare Status   New => Interpretation
Required
2022-03-31 15:56 geoffclare Resolution   Open => Accepted As
Marked
2022-03-31 15:57 geoffclare Final Accepted Text   =>
https://austingroupbugs.net/view.php?id=1555#c5769
2022-03-31 15:57 geoffclare Tag Attached: tc3-2008   
2022-04-21 15:07 agadminInterp StatusPending => Proposed 
2022-04-21 15:07 agadminNote Added: 0005812  
2022-05-23 11:27 agadminInterp StatusProposed => Approved
2022-05-23 11:27 agadminNote Added: 0005843  
2022-06-17 08:34 geoffclare Status   Interpretation Required
=> Applied
==