[issue27808] os.waitpid does not return (0, 0) when child has not exited (FreeBSD)

[Irit Katriel]

Irit Katriel  added the comment:

See also issue34278, issue38802, issue41825.

--
nosy: +iritkatriel

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27808] os.waitpid does not return (0, 0) when child has not exited (FreeBSD)

[Casey Lucas]

New submission from Casey Lucas:

I'm not sure if this a Python issue or a FreeBSD issue but the return value 
from os.waitpid is not reliably (0,0) on FreeBSD when the WNOHANG is used and 
the child process has not yet exited.  Python docs say that the return value 
will be (0,0) but this is not the case.  I believe it is because the FreeBSD 
implementation of waitpid writes an uninitialized value to the status field 
when a child process is not available.  See also: 
http://stackoverflow.com/questions/38984449/is-status-value-from-os-waitpid-unreliable-when-os-wnohang-is-used-under-freebsd

Maybe this is just a documentation issue?  Or does the C code in the Python 
library need to handle this case?

--
components: FreeBSD, Library (Lib)
files: waitpid_test.py
messages: 273167
nosy: Casey Lucas, koobs
priority: normal
severity: normal
status: open
title: os.waitpid does not return (0,0) when child has not exited (FreeBSD)
versions: Python 2.7, Python 3.4
Added file: http://bugs.python.org/file44161/waitpid_test.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com