A NOTE has been added to this issue. ====================================================================== https://www.austingroupbugs.net/view.php?id=1935 ====================================================================== Reported By: corinna_vinschen Assigned To: ====================================================================== Project: 1003.1(2024)/Issue8 Issue ID: 1935 Category: System Interfaces Type: Clarification Requested Severity: Editorial Priority: normal Status: New Name: Corinna Vinschen Organization: Cygwin Project User Reference: Section: posix_spawn_file_actions_addchdir, posix_spawn_file_actions_addclose Page Number: 1590 - 1592 Line Number: 53472 - 53473, 53480 - 53481, 53516 - 53518 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2025-07-07 10:32 UTC Last Modified: 2025-07-24 15:53 UTC ====================================================================== Summary: posix_spawn file actions: in the context of the child or "as if" in the context of the child? ======================================================================
---------------------------------------------------------------------- (0007229) geoffclare (manager) - 2025-07-24 15:53 https://www.austingroupbugs.net/view.php?id=1935#c7229 ---------------------------------------------------------------------- On page 1590 line 53471 section posix_spawn_file_actions_addchdir(), change: <blockquote>[...] all file actions are processed in sequence in the context of the child at a point where the child process is still single-threaded. [...]</blockquote> to: <blockquote>[...] all file actions are processed in sequence as if in the context of the child at a point where the child process is still single-threaded. [...]</blockquote> On page 1591 line 53480 section posix_spawn_file_actions_addchdir(), change: <blockquote>File actions are performed in a new process created by <i>posix_spawn</i>() or <i>posix_spawnp</i>() in the same order that they were added to the file actions object.</blockquote> to: <blockquote>File actions are performed as if in a new process created by <i>posix_spawn</i>() or <i>posix_spawnp</i>() in the same order that they were added to the file actions object.</blockquote> On page 1592 line 53516 section posix_spawn_file_actions_addclose(), change: <blockquote>This transformation shall be as if the specified sequence of actions was performed exactly once, in the context of the spawned process (prior to execution of the new process image), in the order in which the actions were added to the object; additionally, when the new process image is executed, any file descriptor (from this new set) which has its FD_CLOEXEC flag set shall be closed (see [xref to posix_spawn( )]).</blockquote> to: <blockquote>This transformation shall be as if the specified sequence of actions was: <ul> <li>performed exactly once</li> <li>performed in the context of the spawned process (prior to execution of the new process image)</li> <li>performed in the order in which the actions were added to the object</li> </ul> Additionally, when the new process image is executed, any file descriptor (from this new set) which has its FD_CLOEXEC flag set shall be closed (see [xref to posix_spawn( )]).</blockquote> Issue History Date Modified Username Field Change ====================================================================== 2025-07-07 10:32 corinna_vinschenNew Issue 2025-07-24 15:53 geoffclare Note Added: 0007229 ======================================================================
