I cannot duplicate this failure locally, but in GHA the following test
case fails with
Process group 0 != expected 704
child exited with code 1
FAIL winsup.api/spawnpgid.exe (exit status: 1)
I suspect there must be a race between the child process calling getpgid
and the parent running "vchild->p
Dan Harkless via Cygwin writes:
> To be clear, "32-bit" was a modifier to "Cygwin", not to "XEmacs".
> There are no more 32-bit Cygwin maintainers, because it's been
> discontinued, no? That being said, I downloaded the Cygwin list
> archives so I could find the last time I asked about this on t
On Mon, 30 Jun 2025, Corinna Vinschen via Cygwin wrote:
> On Jun 28 12:32, Jeremy Drake via Cygwin wrote:
> > I was looking at setpgid yesterday, and it seems deficient with respect to
> > the errors required to be returned by the POSIX docs in
> > https://pubs.opengroup.org/onlinepubs/9799919799/
On Jun 28 12:32, Jeremy Drake via Cygwin wrote:
> I was looking at setpgid yesterday, and it seems deficient with respect to
> the errors required to be returned by the POSIX docs in
> https://pubs.opengroup.org/onlinepubs/9799919799/functions/setpgid.html
>
> Basically, it seems that setpgid allo
4 matches
Mail list logo