From: Dave Airlie <airlied@gmail.com>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Fw: sigwait() breaks when straced
Date: Mon, 1 Aug 2005 10:12:58 +1000 [thread overview]
Message-ID: <21d7e99705073117121241159a@mail.gmail.com> (raw)
In-Reply-To: <20050801000120.1D00F180EC0@magilla.sf.frob.com>
>
> However, there is in fact no bug here. The test program is just wrong.
> sigwait returns zero or an error number, as POSIX specifies. Conversely,
> sigtimedwait and sigwaitinfo either return 0 or set errno and return -1.
> It is odd that the interfaces of related functions differ in this way,
> but they do.
The someone should fix the manpage, it explicitly says
"The sigwait function never returns an error."
Which is clearly wrong if it can return EINTR...
Dave.
next prev parent reply other threads:[~2005-08-01 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050730170049.6df9e39f.akpm@osdl.org>
2005-08-01 0:01 ` Fw: sigwait() breaks when straced Roland McGrath
2005-08-01 0:12 ` Dave Airlie [this message]
2005-08-01 16:25 ` Jesper Juhl
2005-08-01 19:20 ` Ulrich Drepper
2005-08-01 7:09 ` Ulrich Drepper
2005-08-01 7:57 ` Roland McGrath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21d7e99705073117121241159a@mail.gmail.com \
--to=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox