DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 56TN15VO1111199
Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 56TN15VO1111199
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=E00dbg4A
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A8B5F3858CD1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1753830062;
	bh=RYfQdG7tsLvZwXWKVpFsBovPDUjjJiGNcTNC7xl7iQg=;
	h=Date:To:cc:Subject:In-Reply-To:References:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 From:Reply-To:From;
	b=E00dbg4AxyCSr/QDSfxCFT58aj4KkM/PmlivmfjRUh4loez2EJAnAd1wWiTbRxwqL
	 lhg4ZvP3hyZdNVHMm+yLHiTz4HNUrb5LY0bAJNivCz6eW/Hf/38VyDgD8ik8FDHnPG
	 IhHIqKdaX626hu2wnHfQ4RWm6F22mdJteUl0u/I8=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 3E9483858D26
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 3E9483858D26
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1753829985; cv=none;
 b=kOpVMeW2r13apXX45ospMLYFMe2jraaZxA3o6UxV8pvJ++jH9NI+GPLvOmmEP/nMecSFPmgozunbTZhuM92GsJ0G66jEqPrCESua94kA07fRTkLDk9hbb06a5FRKWzgkzPmlKxShAAkC0nRjL1+VzMYP8/zLl0qcK3+L2NImgZo=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1753829985; c=relaxed/simple;
 bh=jtmyjnDCAv7bddbrrhpPP+yGD3Rs/mplQIvdKTWjF9I=;
 h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version;
 b=GMC/0RWwofxpaBCCvoe9EwxMy8ddjMK/M+QLRTsD6griH9FydhF2OH5p56KudDjP2e5V+KWFLGpKVBPCht0oaK0BTwP6IozQHaY0YXxzMLhg7wmoMHvGckqjOU1XVmVa7Vf3vt4StRqeTALgaeiE6no1sM6v3e42Tih8hEFlTfI=
ARC-Authentication-Results: i=1; server2.sourceware.org
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3E9483858D26
Date: Tue, 29 Jul 2025 15:59:44 -0700 (PDT)
X-X-Sender: jeremyd AT resin DOT csoft DOT net
To: Cedric Blancher <cedric DOT blancher AT gmail DOT com>
cc: cygwin AT cygwin DOT com, cygwin-developers AT cygwin DOT com
Subject: Re: Merge posix_spawn() work with CYGWIN env var switch?
In-Reply-To: <CALXu0Ucquv1ydRb5A_mqNuGA3zWyHiHG05E=C3fkNHrD1rk5QQ@mail.gmail.com>
Message-ID: <0ee4a9ea-e4ad-45c9-2027-a300af4d3ee7@jdrake.com>
References: <CALXu0Ucquv1ydRb5A_mqNuGA3zWyHiHG05E=C3fkNHrD1rk5QQ AT mail DOT gmail DOT com>
MIME-Version: 1.0
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Jeremy Drake via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Jeremy Drake <cygwin AT jdrake DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

On Tue, 29 Jul 2025, Cedric Blancher via Cygwin wrote:

> Good moring!
>
> Could the posix_spawn() work (branch heads/topic/posix_spawn) be
> merged now, but the new version kept off by default unless an option
> in the CYGWIN env var is set?
>
> That would make testing IMO much easier...


It could be, but I don't see how that would help much.  Based on previous
bugs that made it through to release, I am not sure that the snapshot
builds get all that much exercise in the first place.  Also requiring
setting an environment variable to enable the code path would reduce the
exposure even more, to the point that I doubt anyone would use it.  I use
the artifact generated by GitHub Actions to test, and I also backport on
top of 3.6 for testing so I have a 3.6.3 with the posix_spawn patches
which I use to build llvm & clang weekly and rust nightly in GitHub
Actions.


Would it be helpful for me to send a new version of the patch series to
the list for review?  I did update the child_info_spawn::worker args
(mode, prog_arg, and the rest in a const struct reference) and update to
use a local child_info_spawn instance like system and popen now do since
the last version I sent.

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple