-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Geoff Clare wrote:
> For waitpid() the answer lies in the description of the WUNTRACED flag
> on the waitpid() page:
>
> The status of any child processes specified by pid that are
> stopped, and whose status has not yet been reported since they
> stopped, shall also be reported to the requesting process.
>
> It is clear from this that the second call will block.
OK, yes, but the sys/wait.h page says the opposite as well (as I quoted
already):
WIFSTOPPED
True if child is currently stopped.
And this is the only real description of what WIFCONTINUED means. This
description leaves no doubt that the call should not block since it is
still stopped.
> Unfortunately the waitid() page is less clear. The key there is the
> WNOWAIT flag: [...]
This adds to the misery. So, viewing it simplistically, there is more
evidence for not blocking. Note, I don't propose that. It think it
should block. It's just not as simple as pointing to a single phrase in
waitpid. If existing practice is to block then we likely have to take a
look at several man pages.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkhOjTgACgkQ2ijCOnn/RHSnwQCfZtuGROvQU027pSKgxK1BN6zW
EwUAoJs/uft1CvRH82RUAxGJUQaDslJ7
=UwQ4
-----END PGP SIGNATURE-----
|