posix_spawn

[Camm Maguire]

Greetings, and thanks so much!

Mark Geisert via Cygwin-apps <cygwin-apps@cygwin.com> writes:

> On 4/19/2025 1:42 PM, Camm Maguire via Cygwin-apps wrote:
>> Greetings!
>> posix_spawn is returning non-zero without setting errno:
>>    massert(!posix_spawnp(&pid, *p1, &file_actions, &attr,  (void
>> *)p1, environ));
>> Is this intended to be supported?  Is it known to be working or not
>> working elsewhere?
>
> This kind of question should be sent to the main Cygwin mailing list
> cygwin@cygwin.com, now CC'd.  Please follow up there if necessary.
>
> On failure, posix_spawnp() returns the error number rather than
> setting errno.  This is a convention followed by some number of the
> posix_*() functions; which ones is a question for readers of the POSIX
> standard ;-).

Indeed, I read the manpage too quickly -- thanks so much for pointing
this out!

=============================================================================
RETURN VALUE
       Upon successful completion, posix_spawn() and posix_spawnp()  place  the
       PID  of  the  child  process in pid, and return 0.  If there is an error
       during the fork() step, then no child is created, the contents  of  *pid
       are unspecified, and these functions return an error number as described
       below.
=============================================================================

Take care,

>
> ..mark
>
>
>

-- 
Camm Maguire			     		    camm@maguirefamily.org
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah