Bug 159085
Summary: | errno is 0 when sigwait returns an error | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jonathan Kamens <jik> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-05-30 08:43:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jonathan Kamens
2005-05-29 05:42:33 UTC
errno after sigwait is unspecified. See http://www.opengroup.org/onlinepubs/009695399/functions/errno.html and http://www.opengroup.org/onlinepubs/009695399/functions/sigwait.html As sigwait's description doesn't mandate anything about errno value, it is unspecified. The only requirement is that if errno was non-zero before sigwait, it will not be set to 0 by the call. If you see errno becoming 0 when it previously was non-zero, then please provide a testcase. But to my knowledge nothing in glibc violates that requirement, especially not sigwait, which on most architectures will simply not touch errno at all, only return the error value as it is supposed to do. |