[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #61409] The code used to create sub-processes on Windows triggers t

From: Liviu Ionescu
Subject: [bug #61409] The code used to create sub-processes on Windows triggers the spawnve() issue
Date: Mon, 29 Nov 2021 08:30:37 -0500 (EST)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15

Follow-up Comment #8, bug #61409 (project make):

> Your suggestion to modify the Make's own environment also won't work well,
because Make invokes programs asynchronously, i.e. it doesn't wait for the
child to exit, and so modifying Make's environment will affect Make itself

I'm not sure this is accurate, my understanding is that the environment is
copied to the child, so once the child is created, the parent can further
change its own environment unhindered.

> report this bug to Microsoft 

I'm currently investigating on how to report this to Microsoft, but, as I
said, even if Microsoft fixes the bug, millions of older installs will fail.

> and to MinGW64 folks, and hope that they fix it in a future release.

The folks at Mingw-w64 helped with the detailed diagnose. There is not much
they can do. The only thing that is guaranteed to work is to always create the
children processes with a NULL environment, and this is up to the

Remember, the BusyBox sh.exe, which was the first UCRT program to fail when
invoked by make.exe, so the same sh.exe binary works just fine when invoked
from cmd.exe. I'd bet that cmd.exe creates the process with a NULL

So, when I report this to Microsoft, they might very well reply that cmd.exe
works, and if make.exe doesn't, I should report this to GNU make folks. ;-)


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]