The following issue has been UPDATED.
======================================================================
http://austingroupbugs.net/view.php?id=77
======================================================================
Reported By: geoffclare
Assigned To: ajosey
======================================================================
Project: 1003.1(2008)/Issue 7
Issue ID: 77
Category: System Interfaces
Type: Error
Severity: Objection
Priority: normal
Status: Resolved
Name: Geoff Clare
Organization:
User Reference:
Section: 2.4.1
Page Number: 485
Line Number: 16549
Final Accepted Text:
Resolution: Accepted
Fixed in Version:
======================================================================
Date Submitted: 2009-06-29 02:39 UTC
Last Modified: 2009-07-01 14:05 UTC
======================================================================
Summary: 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."
======================================================================
----------------------------------------------------------------------
(0000132) msbrown (manager) - 2009-06-29 02:40
http://austingroupbugs.net/view.php?id=77#c132
----------------------------------------------------------------------
The change above is based on the suggestion made by Philip Guenther
in austin-group-l 11587.
|