| To: | yyyyyyyyyyyyyyy@xxxxxxxxxxxxx |
|---|---|
| Subject: | Defect in XSH sigaction |
| From: | yyy@xxxxxxxxxx |
| Date: | Thu, 9 Feb 2006 01:13:26 GMT |
| Resent-date: | Thu, 9 Feb 2006 08:10:23 +0000 |
| Resent-from: | Andrew Josey <yyyyyy@xxxxxxxxxxxxxxxxx> |
| Resent-message-id: | <1060209081023.ZM6191@xxxxxx> |
| Resent-to: | yyyyyyyyyyyyyyy@xxxxxxxxxxxxx |
Defect report from : Steven Valentine , Hewlett-Packard Company
(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)
@ page 1363 line 42554 section sigaction objection {HPUXESTLSMV200601}
Problem:
Edition of Specification (Year): 2004
Defect code : 3. Clarification required
The restart behavior of interruptible functions which use a timeout
(such as nanosleep and pselect) is not described in sufficient
detail when SA_RESTART is in effect. The duration of the timeout
following the restart varies greatly among implementations.
For example, if a 600ms nanosleep call is interrupted by a signal after 200ms,
and SA_RESTART was used, the observed possibilities on restart are:
1) Do not restart the function, return EINTR immediately.
2) Restart the timeout using the remaining time interval (400ms).
3) Restart the timeout using the original full time interval (600ms).
Action:
Applications should not depend on any particular behavior in this situation.
To make this clear, insert a new sentence before the sentence which starts with
"If the flag is not set...":
If an interruptible function which uses a timeout is restarted, the
the behavior and duration of the timeout following the restart is
undefined.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Defect in XCU 2.6.3, roland.illig |
|---|---|
| Next by Date: | Defect in XSH 2.9.1, rajani.g.k |
| Previous by Thread: | RE: Defect in XSH sigaction, Schwarz Konrad |
| Next by Thread: | Defect in XSH sigaction, Geoff Clare |
| Indexes: | [Date] [Thread] [All Lists] |