[issue20104] expose posix_spawn(p)

Martin Panter report at bugs.python.org
Mon Jan 29 06:23:39 EST 2018


Martin Panter <vadmium+py at gmail.com> added the comment:

Your assumption about calling “file_actions_destroy” would be okay if the posix_spawn_file_actions_t object was a simple object or structure. But I imagine most implementations would allocate memory when you call one of the “add” methods. Especially “addopen”, which is supposed to copy the filename string somewhere. Looking at “uclibc” <https://repo.or.cz/uclibc-ng.git/blob/v1.0.28:/include/spawn.h#l263>, I see it calls “free”, because it allocates an array for all the file actions.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20104>
_______________________________________


More information about the Python-bugs-list mailing list