Austin Group Defect Tracker

Aardvark Mark III


Viewing Issue Simple Details Jump to Notes ] Issue History ] Print ]
ID Category Severity Type Date Submitted Last Update
0000077 [1003.1(2008)/Issue 7] System Interfaces Objection Error 2009-06-29 02:39 2009-10-09 16:51
Reporter geoffclare View Status public  
Assigned To ajosey
Priority normal Resolution Accepted  
Status Interpretation Required  
Name Geoff Clare
Organization
User Reference
Section 2.4.1
Page Number 485
Line Number 16549
Interp Status Approved
Final Accepted Text Note: 0000177
Summary 0000077: stop and cont signals
Description _____________________________________________________________________________
 OBJECTION Enhancement Request Number 14
 gwc:xxxxxxxxxxxxx Defect in XSH 2.4.1 (rdvk# 4)
 [gwc stop and cont signals] Fri, 12 Dec 2008 15:17:48 +0000
 _____________________________________________________________________________

The penultimate paragraph of section 2.4.1 states:

     "When any stop signal (SIGSTOP, SIGTSTP, SIGTTIN, SIGTTOU) is
     generated for a process, any pending SIGCONT signals for that
     process shall be discarded. Conversely, when SIGCONT is generated
     for a process, all pending stop signals for that process shall be
     discarded. When SIGCONT is generated for a process that is
     stopped, the process shall be continued, even if the SIGCONT
     signal is blocked or ignored. If SIGCONT is blocked and not
     ignored, it shall remain pending until it is either unblocked or a
     stop signal is generated for the process."

 This text needs to be updated to take account of threads.

 The change below is based on the suggestion made by Philip Guenther
 in austin-group-l 11587.
Desired Action Replace the paragraph with:

     "When any stop signal (SIGSTOP, SIGTSTP, SIGTTIN, SIGTTOU) is
     generated for a process or thread, all pending SIGCONT signals
     for that process or any of the threads within that process shall
     be discarded. Conversely, when SIGCONT is generated for a process
     or thread, all pending stop signals for that process or any of
     the threads within that process shall be discarded. When SIGCONT
     is generated for a process that is stopped, the process shall be
     continued, even if the SIGCONT signal is ignored by the process
     or is blocked by all threads within the process and there are no
     threads in a call to a sigwait() function selecting SIGCONT.
     If SIGCONT is blocked by all threads within the process, there
     are no threads in a call to a sigwait() function selecting
     SIGCONT, and SIGCONT is not ignored by the process, the SIGCONT
     signal shall remain pending on the process until it is either
     unblocked by a thread or a thread calls a sigwait() function
     selecting SIGCONT, or a stop signal is generated for the process
     or any of the threads within the process."
Tags No tags attached.
Attached Files

- Relationships

-  Notes
(0000132)
msbrown (manager)
2009-06-29 02:40

The change above is based on the suggestion made by Philip Guenther
 in austin-group-l 11587.
(0000177)
ajosey (manager)
2009-08-06 15:40
edited on: 2009-10-09 16:49

Interpretation response
------------------------
The standard states the requirements for the SIGSTOP and SIGCONT 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):
-------------------------------------------------------
Make the change suggested by the submitter


- Issue History
Date Modified Username Field Change
2009-06-29 02:39 msbrown New Issue
2009-06-29 02:39 msbrown Status New => Under Review
2009-06-29 02:39 msbrown Assigned To => ajosey
2009-06-29 02:39 msbrown Name => Mark Brown
2009-06-29 02:39 msbrown Organization => IBM
2009-06-29 02:39 msbrown Section => 2.4.1
2009-06-29 02:39 msbrown Page Number => 485
2009-06-29 02:39 msbrown Line Number => 16549
2009-06-29 02:40 msbrown Note Added: 0000132
2009-06-29 02:40 msbrown Status Under Review => Resolved
2009-06-29 02:40 msbrown Resolution Open => Accepted
2009-07-01 14:05 msbrown Name Mark Brown => Geoff Clare
2009-07-01 14:05 msbrown Organization IBM =>
2009-07-01 14:05 msbrown Reporter msbrown => geoffclare
2009-08-06 15:40 ajosey Note Added: 0000177
2009-08-06 15:40 ajosey Status Resolved => Interpretation Required
2009-08-11 16:32 Don Cragun Interp Status => Pending
2009-09-17 15:41 nick Interp Status Pending => Proposed
2009-10-09 16:49 ajosey Note Edited: 0000177
2009-10-09 16:50 ajosey Interp Status Proposed => Approved
2009-10-09 16:50 ajosey Final Accepted Text => Note: 0000132
2009-10-09 16:51 ajosey Final Accepted Text Note: 0000132 => Note: 0000177


Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker