Message311094
| Author |
martin.panter |
| Recipients |
John Jones, alex, benjamin.peterson, dhduvall, gennad, gregory.p.smith, martin.panter, neologix, pablogsal |
| Date |
2018年01月29日.11:23:39 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1517225019.12.0.467229070634.issue20104@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|