Greetings! Trying to isolate this as you suggest. On first attempt,
copying the exact same strings and calls into a main() function
succeeds. I am near stumped, and can only guess that the addresses
returned by malloc on _init of the file_actions and attr structures is
triggering something. Sug
Greetings! posix_spawnp is returning 10, or ECHILD, on the following
call. At least on my first reading (:-)), ECHILD is not one of the
documented errors for fork, vfork, or clone referenced by the Linux
manpage for posix_spawnp. Suggestions?
Take care,
Greetings, and thanks so much!
Mark Geisert via Cygwin-apps 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
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
